[Mailman-Developers] Need guidance for original GSOC idea
Ibrar Yunus writes: I suggest a project to renovate the seemingly dated website of mailman ( i.e. https://mail.python.org/), That website is based on Mailman 2, and is end-of-life. You should be looking at the postorius project (referred to in the archives of this list: http://www.mail-archive.com/mailman-developers@python.org, and I believe its project repo is at launchpad.net/postorius). and for this, I have skills in web-development (AJAX, JavaScript, JQuery, Bootstrap, Hibernate, Jquery, Python, Java and PHP servers...etc). If this idea has potential, Check the GSoC FAQ. I am pretty sure website design as such is out of bounds for GSoC. The Postorius developers are probably interested in people to help write code to extend its functionality, however. If it happens to be pretty at the same time, so much the better! Steve ___ 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'15
Florian Fuchs writes: Am 16.03.2015 um 14:50 schrieb Sagar Ghai: Hi, I would be interested in contributing to one of the projects named: anonymous lists as part of GSOC'15. I am a second year undergraduate student at IIT-Mandi, India. Can someone let me know how to move forward with this. Hi Sagar, there has already been quite a bit of discussion about this project on this list. You could start by checking the archives and read what has been discussed so far. I'm sure this will get you started pretty well. But start by reading the project page, especially the section Mentors are Not Teachers, and the linked essay How to SPAM. You need to be the active party here. Nobody has interest in mentoring a student who needs to be told what the next step is all the time. Good luck! ___ 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] Query regarding auto-reply mechanism
Aanand Shekhar Roy writes: Please ignore the above mail, it was sent on 5th march, i dont know why it came today . These things happen in Internet mail, through no fault of anybody in particular. Don't worry about it. The courtesy notice is helpful though, thank you! On the other hand, figuring out *why* it happened on a Mailman list would be a good exercise for a new Mailman developer. :-) ___ 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] Query regarding auto-reply mechanism
Please ignore the above mail, it was sent on 5th march, i dont know why it came today . ___ 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/2013001%40iiitdmj.ac.in 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] contributing to gnu mailman development and preparing to gsoc 2015
On Monday 16 March 2015 06:37 PM, Asif Saifuddin wrote: I'm interest inContinuous Integration for Mailman Suite Setting up continuous integration for all mailman projects with support for different database backends (sqlite and pgsql are a must, others should be easy to add). It should also enable developers to test their separate branch. Look up travis-ci if you have no idea what continuous integration means. will this interest the mailman devs? which servers mailman use? ubuntu? debian? versions? should use jenkins with buidbot? or travis CI? These are the questions you need to answer to create the proposal, none of the mentors are going to answer them for you. Please read through the archives of this list and you'd find a *lot* of material to start on this project. -- thanks, Abhilash signature.asc Description: OpenPGP digital 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] contributing to gnu mailman development and preparing to gsoc 2015
that was helpful ! thank you :) will come up with some ideas soon On Mon, Mar 16, 2015 at 7:12 PM, Abhilash Raj raj.abhila...@gmail.com wrote: On Monday 16 March 2015 06:37 PM, Asif Saifuddin wrote: I'm interest inContinuous Integration for Mailman Suite Setting up continuous integration for all mailman projects with support for different database backends (sqlite and pgsql are a must, others should be easy to add). It should also enable developers to test their separate branch. Look up travis-ci if you have no idea what continuous integration means. will this interest the mailman devs? which servers mailman use? ubuntu? debian? versions? should use jenkins with buidbot? or travis CI? These are the questions you need to answer to create the proposal, none of the mentors are going to answer them for you. Please read through the archives of this list and you'd find a *lot* of material to start on this project. -- thanks, Abhilash ___ 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] contributing to gnu mailman development and preparing to gsoc 2015
I'm interest inContinuous Integration for Mailman Suite Setting up continuous integration for all mailman projects with support for different database backends (sqlite and pgsql are a must, others should be easy to add). It should also enable developers to test their separate branch. Look up travis-ci if you have no idea what continuous integration means. will this interest the mailman devs? which servers mailman use? ubuntu? debian? versions? should use jenkins with buidbot? or travis CI? regards Asif On Wed, Mar 4, 2015 at 5:24 PM, Asif Saifuddin auv...@gmail.com wrote: Thank you! I will try to dig easy bug and write tests for them. On Wed, Mar 4, 2015 at 2:57 PM, Abhilash Raj raj.abhila...@gmail.com wrote: Hi Asif, On Wednesday 04 March 2015 12:57 PM, Asif Saifuddin wrote: Dear Mailman developers, I'm Asif Saifuddin from Dhaka Bangladesh, Student of Masters at IIT, Jahangirnagar University. I am python programmer with django+django rest framework experince. I saw some projects of mailman have django and django rest framework codes. So I am planning to contribute to some related issues matching my skills and can prepare myself to get selected for gsoc 2015. There are a few projects listed on out Ideas Page that do have Django as a requirement. For beginner friendly bugs we suggest that you dig through bug tracker of 'Postorius'(The Mailman3's webui) or try to write tests for Postorius. -- thanks, Abhilash Raj ___ 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 '15 : Student applications start today
GSoC Applicants, The student application period for Google Summer of Code 2015 starts from today (March 16 at 19:00 UTC). We encourage each of you to submit your proposal as soon as possible on melange, since it has been known to crash in the days near to deadline. You can edit your proposal as many times you like till the deadline. In past we have been following the application template from PSF and this year too there is no change in that front. You can find it here[1]. Remember that blogging is an important part of GSoC and thus it is must that you have your personal blog setup along with RSS/ATOM feeds. Feeds helps us to follow your blogs without visiting the webpage everytime. If you have problem setting up just sign up on on Blogger[2]). [1]: https://wiki.python.org/moin/SummerOfCode/ApplicationTemplate2015 [2]: https://www.blogger.com/ All the best! -- thanks, Abhilash signature.asc Description: OpenPGP digital 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] Need guidance for original GSOC idea
Dear Mailman developers, I have been looking through the ideas for GSoC 2015, and a few interested me. Other than being a Computer Science student, I also have much experience in Graphics Design and Digital Art(examples: https://www.facebook.com/pages/The-Art-of-Ibrar-Yunus/168155153339571 ); I suggest a project to renovate the seemingly dated website of mailman ( i.e. https://mail.python.org/), and for this, I have skills in web-development (AJAX, JavaScript, JQuery, Bootstrap, Hibernate, Jquery, Python, Java and PHP servers...etc). If this idea has potential, kindly reply me soon as possible. So that I may send you a few concept designs for your website; and can refine my GSoC application. Kind Regards, Ibrar Yunus ___ 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'15
Hi, I would be interested in contributing to one of the projects named: anonymous lists as part of GSOC'15. I am a second year undergraduate student at IIT-Mandi, India. Can someone let me know how to move forward with this. ___ 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'15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.03.2015 um 14:50 schrieb Sagar Ghai: Hi, I would be interested in contributing to one of the projects named: anonymous lists as part of GSOC'15. I am a second year undergraduate student at IIT-Mandi, India. Can someone let me know how to move forward with this. Hi Sagar, there has already been quite a bit of discussion about this project on this list. You could start by checking the archives and read what has been discussed so far. I'm sure this will get you started pretty well. Florian ___ 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/f%40florianfuchs.com Security Policy: http://wiki.list.org/x/QIA9 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVBw4FAAoJEEceGbPdavl7GcIH+gMFTEP7S0fgxfEE/NNqGnKG StkVGbL+vwmtzJsEZCv6Tse0q/8H3sQA9ZMBZaUEMgLAyrTJsQLtwNoMOIyVFNn2 u3IWyUp5QXs5qM0FAMw5Ec65eodYtc9PrpSGioNc97S/E6OKZmvKf9q45PC27boF /SD7q7ZGHglVGTcXAJqs+jrJEFUYsvEr1GY7hrnCAnM3/fCpbL1SRVGALGfKsVL8 tWUknjsCFmmDPy5Rn8kO6lqghmHjkClXQWdD9Zjqnu+OXoT5Cf4bvYiwjwdX2WVo 9M2W/cXwNT+IF7VADVF6Iv14Y2jGTEdpsBqrPKeMX/n8NlxIELHkRogU+CmY68U= =5/hs -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] Query regarding auto_reply mechanism
On 03/11/2015 11:52 PM, Stephen J. Turnbull wrote: Aanand Shekhar Roy writes: Please ignore the above mail, it was sent on 5th march, i dont know why it came today . These things happen in Internet mail, through no fault of anybody in particular. Don't worry about it. The courtesy notice is helpful though, thank you! On the other hand, figuring out *why* it happened on a Mailman list would be a good exercise for a new Mailman developer. :-) Actually, It didn't happen 'on a Mailman list'. And it did happen also to the follow-up message and Steve's reply. The issue is that the server's MTA has some rules for holding or discarding messages based on regexp matches against the message's headers. In this case, the string auto-reply in the Subject: caused the messages to be put in Postfix's HOLD queue where they sat for some time before being released. You will note I changed that to auto_reply in this reply. The particular regexp should probably be more restrictive. Presumably it is intended to catch out of office type messages. I'm not sure what a better regexp would be, but I don't control the Postfix configuration on this server anyway. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan ___ 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
Re: [Mailman-Developers] [Queries] Related to List Styles in mailman
hi, The advantage of first is that we will gonna have all the styles at a single place and no need to call for the default page from other places as we will gonna do in the second method. Here but we have to apply the constraints on the default entries and not on other entries. On other hand in second point we will have a unify table with same functionality for all the entries but we have to call the default styles which will be at different place. Thanks, Prakhar Joshi DA-IICT,Gandhinagar On Mon, Mar 16, 2015 at 8:48 AM, Stephen J. Turnbull step...@xemacs.org wrote: prakhar joshi writes: hi, I am Prakhar Joshi (irc name :- _pjoshi). I have few things to discuss about the storage of new styles for the list that will be created through rest API. I think we should create a separate table for the list styles and there we can add the entries for the newly created styles in those tables. Now we have to work around for storing these default styles in the database. Here what I think is we can do it in 2 ways :- 1) We have two default entries in the table and can only have GET request for these two and GET/POST request for rest of the entries in the table. 2) We can have these 2 default styles out of the table and these 2 can be called as they are now from their places in the web interface directly. What are the advantages and disadvanatages of the two approaches as far as you are concerned? Steve ___ 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] Reagarding A Dashboard for Admins/Owners/Moderators
Shreyas Lakhe writes: Ihttps://moqups.com/srlakhe/weZugpFL The I is a typo? Note that Activity should be tri-state: approved, rejected, pending. In the case of held messages, there may be more states (each reason for holding mail could be treated as a separate state). ___ 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, Anonymous Lists
Pavan Koli writes: (a generally good description of an approach to the problem) hidden from him. But if someone tries to spam the mailing list, that person can be caught by noting his anonymous id. I'm not sure what use case you have in mind. Why would a spammer post to the anonymous list from the same address twice? If subscription (and posting) requires owner approval, such spamming is very rare anyway. 3. I didn't come across a single mailing list for whistleblowers, activists, or people trading very sensitive information. You won't. They have alternative channels for transmitting information, just like spies employed by governments or corporations. Mail spoofing attempts can be stopped by encrypting mails, Encrypted lists is a different use case. You'd use digital signatures in this case. using PGP, but there is one problem. The person encrypting the mail would have to share their public key with everyone on the mailing list, which can be a tedious task as the mailing lists keep on changing in size, Key distribution in this case is easy. Just post it to the mailing list. :-) and also mails can be leaked if public key falls into wrong hands. This isn't a real use case. Think carefully about your definition of wrong hands in the context of whistleblower. I've come up with a solution for this, these mailing lists will be kept in a very different category from others. Here when ever a user will register, they'll have to also provide their public key. This is in fact the same basic approach as a previous GSoC project which hasn't been integrated yet. Problem- The list manager has to be authentic, using their public key list subscribers can verify their authenticity I don't understand what you mean. (Or I propose a public key for the list itself and then people can use it to verify lists authenticity). I think this is the right solution anyway. One possibility would be to use DKIM signature technology (RFC 6376, I think). ___ 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] Contributing to GNU Mailman (GSOC '15)
Hi, I now understand there projects a lot more than I did when I previously posted. I want to work on the 'Dashboard for Admins', I have worked in some details that I think should be in the admin page. 1. This would be the main page - https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:ae312b9e8 1. The admin can mass subscribe from the 'Subscriber Request' widget https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:af543c52c 2. The List settings would take user to a different page for managing a particular list - modify list name, delete list, info about the list, admin/moderator role management, current subscribers (mass ban and unsubscribe, though I know that ban would mostly occur through next point) 3. The 'Mail approvals' give a stat and clicking on a particular list or list from 'list archive page' would take admin to https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a5a5aaa3c 1. The activities are grouped in a sense that the admin can look on new, pending mail requests and also look at posts that are marked as moderation needed. 2. When admin clicks on some post from the left pane, the right pane would focus on that particular post. Admin can then accept, reject or mark the post as pending and can also ban the user from there. 3. The subscribers link in the left pane would show all the subscribers to that list and the admin can then ban/unsubscribe from there. 4. The List Setting link will take to point (1b) 2. I also think a need for user page ( different from the subscriber's page, this could be viewed by the public and not only other fellow subscribers. The motivation behind it is that a user could also be an admin too and thus there is a need for consistency. Like this https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a459f6c6a) 1. From here user can have profile control https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a16afdd67 2. User can go to the admin dashboard from there. And start a list. Coming to execution of the design, I ought to aim for completing point (1) completely at the start and then going to point (2) (which I think is doable as well). As of now, I haven't worked on any bug as of yet, I will asap set the development environment, look at the code and report back to you. Do give remarks to this workflow. -Ankush Jindal Student, IIT Mandi, India Phone: +91-9805901195 Github: travis-bickle On Sun, Mar 15, 2015 at 11:53 AM, Abhilash Raj raj.abhila...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ankush, On Sunday 15 March 2015 07:08 AM, Ankush Jindal wrote: Hi Sir, I am Ankush Jindal, pursuing Computer Science from IIT Mandi, India. I have hands on with both python and javascript. I would definitely want to work this summer for GNU Mailman. I however, would like to suggest a modified version of already proposed project(s). I went through 16 Brainstorm Ideas For Mailman’s Web Interface http://blog.linuxgrrl.com/2012/03/13/mailman-brainstorm/ and I thought of integrating point 6, 9, 11, 12, 13 and 14. That is, I am picturing mailman with- A) User Profile ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#Subscriber_profile_pages ) B) Admin Page ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#A_Dashboard_for_Admins.2FOwners.2FModerators ) C) Give more UX controls to the mail list like timeline, metadata, user and post filtering and anonymous posting ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#Anonymous_lists, this could be a stretch goal) I suggest that you read through the ideas page more carefully and ask if you have any specific doubts. All of these projects have been discussed in details on this very mailing-list. Please scroll through the archives (link in the footer) and read more about them. Also, I would suggest that you choose any one of the Ideas instead trying to implement all three of them. All of them are fairly big enough for a summer (although, that does depend on your proposal). However, I have a little hesitation that I am a little late in discussing the project and I am really sorry for it. I promise to make it up to you, if you could advise me some particular warm-up tasks or some other exercise that you require from me, given the time-frame, I would be more than happy to do so. You can get started by setting up your development environment and fixing atleast 1 bug for any of the projects listed on the Ideas Page. There should be link to bug-trackers in there too. - -- thanks, Abhilash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVBSVHAAoJEJ2bK6Bh0KZ8ZUcP/2sjzUQppmwF3NasC9L3ZVLr KLINxAFXexHnfS48FltzBQGhrtvfDOJTfD3aQLjnZAwootuXfsDW5O5/nh2OxE4y
Re: [Mailman-Developers] Contributing to GNU Mailman (GSOC '15)
Hi, I now understand there projects a lot more than I did when I previously posted. I want to work on the 'Dashboard for Admins', I have worked in some details that I think should be in the admin page. 1. This would be the main page - https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:ae312b9e8 1. The admin can mass subscribe from the 'Subscriber Request' widget https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:af543c52c 2. The List settings would take user to a different page for managing a particular list - modify list name, delete list, info about the list, admin/moderator role management, current subscribers (mass ban and unsubscribe, though I know that ban would mostly occur through next point) 3. The 'Mail approvals' give a stat and clicking on a particular list or list from 'list archive page' would take admin to https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a5a5aaa3c 1. The activities are grouped in a sense that the admin can look on new, pending mail requests and also look at posts that are marked as moderation needed. 2. When admin clicks on some post from the left pane, the right pane would focus on that particular post. Admin can then accept, reject or mark the post as pending and can also ban the user from there. 3. The subscribers link in the left pane would show all the subscribers to that list and the admin can then ban/unsubscribe from there. 4. The List Setting link will take to point (1b) 2. I also think a need for user page ( different from the subscriber's page, this could be viewed by the public and not only other fellow subscribers. The motivation behind it is that a user could also be an admin too and thus there is a need for consistency. Like this https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a459f6c6a) 1. From here user can have profile control https://moqups.com/jindal.ankus...@gmail.com/2Mm42VyL/p:a16afdd67 2. User can go to the admin dashboard from there. And start a list. Coming to execution of the design, I ought to aim for completing point (1) completely at the start and then going to point (2) (which I think is doable as well). As of now, I haven't worked on any bug as of yet, I will asap set the development environment, look at the code and report back to you. Do give remarks to this workflow. -Ankush Jindal Student, IIT Mandi, India Phone: +91-9805901195 Github: travis-bickle ___ 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] Contributing to GNU Mailman (GSOC '15)
Sorry for posting it twice. The links were not working in previous posts (they had email-id and hence truncated). Consider this mail as the reply. Hi, I now understand there projects a lot more than I did when I previously posted. I want to work on the 'Dashboard for Admins', I have worked in some details that I think should be in the admin page. 1. This would be the main page - https://moqups.com/jankush95/2Mm42VyL/p:ae312b9e8 1. The admin can mass subscribe from the 'Subscriber Request' widget *https://moqups.com/jankush95/2Mm42VyL/p:af543c52c https://moqups.com/jankush95/2Mm42VyL/p:af543c52c* 2. The List settings would take user to a different page for managing a particular list - modify list name, delete list, info about the list, admin/moderator role management, current subscribers (mass ban and unsubscribe, though I know that ban would mostly occur through next point) 3. The 'Mail approvals' give a stat and clicking on a particular list or list from 'list archive page' would take admin to *https://moqups.com/jankush95/2Mm42VyL/p:a5a5aaa3c https://moqups.com/jankush95/2Mm42VyL/p:a5a5aaa3c* 1. The activities are grouped in a sense that the admin can look on new, pending mail requests and also look at posts that are marked as moderation needed. 2. When admin clicks on some post from the left pane, the right pane would focus on that particular post. Admin can then accept, reject or mark the post as pending and can also ban the user from there. 3. The subscribers link in the left pane would show all the subscribers to that list and the admin can then ban/unsubscribe from there. 4. The List Setting link will take to point (1b) 2. I also think a need for user page ( different from the subscriber's page, this could be viewed by the public and not only other fellow subscribers. The motivation behind it is that a user could also be an admin too and thus there is a need for consistency. Like this *https://moqups.com/jankush95/2Mm42VyL/p:a459f6c6a https://moqups.com/jankush95/2Mm42VyL/p:a459f6c6a*) 1. From here user can have profile control *https://moqups.com/jankush95/2Mm42VyL/p:a16afdd67 https://moqups.com/jankush95/2Mm42VyL/p:a16afdd67* 2. User can go to the admin dashboard from there. And start a list. Coming to execution of the design, I ought to aim for completing point (1) completely at the start and then going to point (2) (which I think is doable as well). As of now, I haven't worked on any bug as of yet, I will asap set the development environment, look at the code and report back to you. Do give remarks to this workflow. -Ankush Jindal Student, IIT Mandi, India Phone: +91-9805901195 Github: travis-bickle *Ankush Jindal* *Student, IIT MandiRoom 402, Suvalsar Hostel, MandiIIT Mandi, Himachal Pradesh.Phone: +91-9805901195* *Facebook: @*jindalankush95 http://facebook.com/jindalankush95 On Sun, Mar 15, 2015 at 11:53 AM, Abhilash Raj raj.abhila...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ankush, On Sunday 15 March 2015 07:08 AM, Ankush Jindal wrote: Hi Sir, I am Ankush Jindal, pursuing Computer Science from IIT Mandi, India. I have hands on with both python and javascript. I would definitely want to work this summer for GNU Mailman. I however, would like to suggest a modified version of already proposed project(s). I went through 16 Brainstorm Ideas For Mailman’s Web Interface http://blog.linuxgrrl.com/2012/03/13/mailman-brainstorm/ and I thought of integrating point 6, 9, 11, 12, 13 and 14. That is, I am picturing mailman with- A) User Profile ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#Subscriber_profile_pages ) B) Admin Page ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#A_Dashboard_for_Admins.2FOwners.2FModerators ) C) Give more UX controls to the mail list like timeline, metadata, user and post filtering and anonymous posting ( http://wiki.list.org/DEV/Google_Summer_of_Code_2015#Anonymous_lists, this could be a stretch goal) I suggest that you read through the ideas page more carefully and ask if you have any specific doubts. All of these projects have been discussed in details on this very mailing-list. Please scroll through the archives (link in the footer) and read more about them. Also, I would suggest that you choose any one of the Ideas instead trying to implement all three of them. All of them are fairly big enough for a summer (although, that does depend on your proposal). However, I have a little hesitation that I am a little late in discussing the project and I am really sorry for it. I promise to make it up to you, if you could advise me some particular warm-up tasks or some other exercise that you require from me, given the time-frame, I would be more than happy to do
