Re: [Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
Thank you all for your feedback. Previously, what I was going for was a multipage dashboard with varying functionality. I will now change my design, which will be something of a single page dashboard allowing the admin to do his daily tasks with ease and other tasks such as creating new lists etc. Also Stephen mentioned that somethings are a part of mailman core. If it is required, I can work on mailman core ( I am experienced in python ) I also showed Abhilash a rough mock-up of my idea. I will make appropriate changes to the mock-up and show it to you. To florian - The bug thing was kind of my fault, I submitted a patch and wanted to know any mentor's opinion on that, and then I would have sent a merge request. To all - I ,now ,basically have a much better idea and understanding on how to implement this.Thank you all. One last thing though, Is there anything else left to be discussed in dashboard idea ( something obvious that I may have missed out) ? Yash Mehrotra yashmehrotr...@gmail.com On Mon, Mar 16, 2015 at 11:15 PM, Florian Fuchs f...@florianfuchs.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.03.2015 um 12:20 schrieb Yash Mehrotra: 5. We also also give each list its individual page, so the admin can do list specific functions like, say change settings , ban user etc. That's probably out of the scope of this project. The lists already have moderation/settings pages. No need to redo this. If something can be improved on that end, it's probably part of a separate effort. *Bug Fixes* I have also submitted a patch for a bug in postorius ( waiting for some to look at it) and am also working on a bug in Mailman core. I can't see a merge proposal from you for postorius, could you check if your bugfix branch is proposed for merging? Oh, and don't forget to add a link to the MP to your application. Florian -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVBxbNAAoJEEceGbPdavl7bP0H/jY1J05viF+FqaL6GhtJUAwT /yI8nmFKExOiuieG7M0+TWkVJZ82ztzhHyV6ekQE9gzRhPD6yLbGzRk28USpKU1h itP87X0oijbw2zA/zsCpkeN0a81Zkr4ai+eINH1nDGgExdOA+Jr30mrbc/FwLREF h73Pi9KBrSSVu9p38RwKI077NSWaeN3qkAlNc2Map6cVNx8W+5UqP/FNCNNSAWnD VY+c+hoPwvPtpvUfVWjTBZXiaLZFTRx98t42Pav6ZxvUoEmqeyUP7KIDgeAlOwaE ScQu/7bJI7Vvt5ggbFuYExTvZHMOo3JOuP/AbyiTHKiZANZmevQ7R1Ip/+BA0Jw= =9xlG -END PGP SIGNATURE- ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/yashmehrotra95%40gmail.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
On Fri, Mar 13, 2015 at 7:20 AM, Yash Mehrotra yashmehrotr...@gmail.com wrote: 6. One more cool feature would be to color code different types of things for visual ease. Eg. Subscription requests can be color A. Held messages can be color B. and so on. This will not only help the administrator but also would visually good to look at. Make sure that if you DO do this, that it is accessible for those with disabilities (visual impairments, cognitive disabilities, etc.) -- Bryan Carbonnell - carbo...@gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting What a great ride! ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.03.2015 um 12:20 schrieb Yash Mehrotra: 5. We also also give each list its individual page, so the admin can do list specific functions like, say change settings , ban user etc. That's probably out of the scope of this project. The lists already have moderation/settings pages. No need to redo this. If something can be improved on that end, it's probably part of a separate effort. *Bug Fixes* I have also submitted a patch for a bug in postorius ( waiting for some to look at it) and am also working on a bug in Mailman core. I can't see a merge proposal from you for postorius, could you check if your bugfix branch is proposed for merging? Oh, and don't forget to add a link to the MP to your application. Florian -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVBxbNAAoJEEceGbPdavl7bP0H/jY1J05viF+FqaL6GhtJUAwT /yI8nmFKExOiuieG7M0+TWkVJZ82ztzhHyV6ekQE9gzRhPD6yLbGzRk28USpKU1h itP87X0oijbw2zA/zsCpkeN0a81Zkr4ai+eINH1nDGgExdOA+Jr30mrbc/FwLREF h73Pi9KBrSSVu9p38RwKI077NSWaeN3qkAlNc2Map6cVNx8W+5UqP/FNCNNSAWnD VY+c+hoPwvPtpvUfVWjTBZXiaLZFTRx98t42Pav6ZxvUoEmqeyUP7KIDgeAlOwaE ScQu/7bJI7Vvt5ggbFuYExTvZHMOo3JOuP/AbyiTHKiZANZmevQ7R1Ip/+BA0Jw= =9xlG -END PGP SIGNATURE- ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.03.2015 um 03:04 schrieb Stephen J. Turnbull: Yash Mehrotra writes: *My Ideas - * 1. One issue currently as mentioned is owners of multiple lists have to go through all the pages for changes. I think we should show all the mailing list's requests,subscriptions etc. all in one page. This isn't a dashboard-level issue; this should be a facility at the core level -- the core knows which lists the user is responsible for, and what the pending tasks are for each. Are you sure Mailman 3 + Postorius doesn't have this capability already? Sure, implenting such a user-based lookup of all roles and action-items in the core-API would facilitate things on the UI side. Currently this would involve several different HTTP calls to collect the data. But I think this is an implementation detail (and ideally possible solutions for this are part of any application for this project). To me the most important feature of the dashboard is exactly this: A single spot to show me where action from my side is required. 2. The new list features should be opened from a different tab as a list admin doesnt do this every day. *The primary focus should be - to make it easy for an admin to do his daily activities.* I agree with the general statement, but are the new list operations really a problem if displayed on the main dashboard? 3. So, the index page will contain stuff mentioned on point 1, and the there will be different pages for other stuff like - create/delete list, view statistics ( see next point) My experience with a non-web-based moderation system is that most moderation/subscription requests can be judged from a one-line display, and for more complex operations (eg, banning an apparently abusive would-be subscriber) use Web 2.0 tech like Javascript popup menus. Of course they have to degrade gracefully if JS is disabled, and even if CSS is disabled. But the main interface probably can include list creation/deletion and a few interesting stats. That's what we currently have on the list-specific message moderation pages in postorius: A single row for each message, details (body/headers) in a model window if needed. IMO this could look similar on the dashboard. 6. One more cool feature would be to color code different types of things for visual ease. Eg. Subscription requests can be color A. Held messages can be color B. and so on. This will not only help the administrator but also would visually good to look at. Maybe. On the other hand, maybe users will prefer to have the tasks grouped (a group for subscription requests, a group for moderation, a group for admin-initiated actions like list creation if permitted, etc). Maybe color coding will look nice, but IMHO it's unlikely to be a big efficiency enhancement compared to grouping. I think you need to a bit careful here. Different colors might make it easier to distinguish between types of action items, but they will most likely also introduce an implicit prioritization. But IMO the priority of different types of action items can vary a lot depending on lists' characteristics. Also, every admin might have a personal idea of what's important and what's not. Florian -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVBxSgAAoJEEceGbPdavl7QwUIAKL/vHVfznp2mjzeKjssTZRq 1T5gLfqP1qRHUNO58bBX9b1jyZYqMCea6lXL3Zt6x2pEKka7tiIr84cysBXhcJtA OfB7oaUujpjExKFlPrTMFwwSyj+Gp4R213wloKtM78jcTE0OLas6oZt4dnywiec0 AglOyDqqfkK4kyjkNeLc9wG8cvrtu5/QRAxWKVtvjir9UH38CYT0TFzXM9TEOuY/ oegEMj2+082eVe1hDHm3jjRQ7Qg4qGY26QnFonS5asdVZaZopX34+wxfRNpKMY9r eZ9Ef/L9gnMfs6ddg5Lty4+43PyQTlafj61NWkHJqzvUAG0EMkyUSQs1mxNJWfE= =1zw2 -END PGP SIGNATURE- ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
Yash Mehrotra writes: *My Ideas - * 1. One issue currently as mentioned is owners of multiple lists have to go through all the pages for changes. I think we should show all the mailing list's requests,subscriptions etc. all in one page. This isn't a dashboard-level issue; this should be a facility at the core level -- the core knows which lists the user is responsible for, and what the pending tasks are for each. Are you sure Mailman 3 + Postorius doesn't have this capability already? 2. The new list features should be opened from a different tab as a list admin doesnt do this every day. *The primary focus should be - to make it easy for an admin to do his daily activities.* I agree with the general statement, but are the new list operations really a problem if displayed on the main dashboard? 3. So, the index page will contain stuff mentioned on point 1, and the there will be different pages for other stuff like - create/delete list, view statistics ( see next point) My experience with a non-web-based moderation system is that most moderation/subscription requests can be judged from a one-line display, and for more complex operations (eg, banning an apparently abusive would-be subscriber) use Web 2.0 tech like Javascript popup menus. Of course they have to degrade gracefully if JS is disabled, and even if CSS is disabled. But the main interface probably can include list creation/deletion and a few interesting stats. 4. We can also provide some basic statistics for a mailing list like which user is most active, how many avg, mails are sent in a day etc. I don't understand why this belongs specifically on an admin dashboard. In most cases subscribers probably care more about it than admins do. 5. We also also give each list its individual page, so the admin can do list specific functions like, say change settings , That's an ancient interface, and doesn't really come up to the expectations people have when they hear dashboard. All your pending tasks (including those you initiate like list creation) should be available conveniently as soon as you log in, and as much as possible which features are available should not depend on the currently. ban user etc. This will almost certainly turn out to be horrible UI. Experience shows that banning a user based on an abuse detected during moderation or subscription approval, and so it should be available without leaving the dashboard. 6. One more cool feature would be to color code different types of things for visual ease. Eg. Subscription requests can be color A. Held messages can be color B. and so on. This will not only help the administrator but also would visually good to look at. Maybe. On the other hand, maybe users will prefer to have the tasks grouped (a group for subscription requests, a group for moderation, a group for admin-initiated actions like list creation if permitted, etc). Maybe color coding will look nice, but IMHO it's unlikely to be a big efficiency enhancement compared to grouping. I will add more stuff based on your feedback. Sorry, that's not the way this works. Part of GSoC to determine requirements. You tell us what you plan to do, we decide whether we like it better than somebody else's proposal. Most likely, if you seem to have overestimated your productivity we'll tell you you can cut back your proposal, and where to cut. But if you propose something trivial, mostly you'll get the simple comment this is not enough to be a good GSoC project. A dashboard that gives convenient access to all tasks a user is assigned seems like a GSoC-sized project to me (maybe bigger). The main thing you need to add is a schedule. See also http://turnbull.sk.tsukuba.ac.jp/Blog/SPAM.txt. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
Hi all I wanted to apply for the project - Dashboard for Admins/Owners/Moderators. I went through the archives and read about what was required. I also researched outside and saw how other companies used the dashboard to full effects. *My Ideas - * 1. One issue currently as mentioned is owners of multiple lists have to go through all the pages for changes. I think we should show all the mailing list's requests,subscriptions etc. all in one page. Eg. a...@xyz.com wants to join list1, d...@qwe.com wants to join list 2 etc. ( Different list's requests can be handled simultaneously) 2. The new list features should be opened from a different tab as a list admin doesnt do this every day. *The primary focus should be - to make it easy for an admin to do his daily activities.* 3. So, the index page will contain stuff mentioned on point 1, and the there will be different pages for other stuff like - create/delete list, view statistics ( see next point) 4. We can also provide some basic statistics for a mailing list like which user is most active, how many avg, mails are sent in a day etc. 5. We also also give each list its individual page, so the admin can do list specific functions like, say change settings , ban user etc. 6. One more cool feature would be to color code different types of things for visual ease. Eg. Subscription requests can be color A. Held messages can be color B. and so on. This will not only help the administrator but also would visually good to look at. I will add more stuff based on your feedback. About me - I am a Computer Science student at JIIT - Noida. *Bug Fixes* I have also submitted a patch for a bug in postorius ( waiting for some to look at it) and am also working on a bug in Mailman core. To all the mentors, please give your feedback about the ideas, and what all more stuff could be added and what should be improved. Thank You, Yash Mehrotra yashmehrotr...@gmail.com ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
