Mailman 3 March 2015 - Mailman-Developers

Re: [Mailman-Developers] [Queries] Related to List Styles in mailman
by Florian Fuchs 17 Mar '15

17 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 15.03.2015 um 22:34 schrieb prakhar joshi: > 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. Are these suggestions alternatives to the existing list style functionality[1] or should they be build on top of that? Florian [1] As described in Barry's answer: http://www.mail-archive.com/mailman-developers%40python.org/msg15408.html (see the code in src/mailman/styles for details) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVCATqAAoJEEceGbPdavl7Oe4H/RT2AzLhGZhUSczwZMu6ZTww N5tWYx0XGnoW3HT6mnZPRF1qNqjdQJt/4VLN7XFSBeGWZxI5DlngF79ASOlQYB1C uROegv32Fx97BpRPc/7XqTZ/Y1piij8gSxCbmRnVjV5AfcZavDmLzga7rjdrQ7zM rkiy6scWmWrZBU33UGoOU48UZ/iY6I7kqjl/Xc6IcHr7HnWC/yHx2F/KCqzHs1um ZPAnyVCb+i1k9GlfZHYOngDzKjF40BbbgA5da3IktBMcSqAdPuPZlkO9kT8YDK4H r/wGhAgAVGQos2YIKFN+HQc1xMvvxAFbMjCYIobx3VNEeTjvC1zLojXQxnlDqgc= =s8oV -----END PGP SIGNATURE-----

1 0

Re: [Mailman-Developers] Gsoc'15
by Florian Fuchs 16 Mar '15

16 Mar '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(a)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… > > 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-----

2 1

Need guidance for original GSOC idea
by Ibrar Yunus 16 Mar '15

16 Mar '15

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

2 1

GSOC - Dashboard for Admins/Owners/Moderators
by Stephen J. Turnbull 16 Mar '15

16 Mar '15

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.

2 1

Query regarding auto-reply mechanism
by Aanand Shekhar Roy 16 Mar '15

16 Mar '15

Hi , I have a doubt regarding auto-responding Suppose I have posted my confidential information on mailing list, and the list setting is neither "accept" nor "discard" any mails having confidential information.Whether it should be posted or not depends on the user .So I had to ask which one approach is better? 1.Including a command like "accept_confidential" at start of message or subject. or 2.Sending the mail, getting an auto-reply from reply-bot like " your mail contains confidential info. reply with "confirm" ".

3 3

Re: [Mailman-Developers] GSOC - Dashboard for Admins/Owners/Moderators
by Bryan Carbonnell 16 Mar '15

16 Mar '15

On Fri, Mar 13, 2015 at 7:20 AM, Yash Mehrotra <yashmehrotra95(a)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 - carbonnb(a)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!"

1 0

Gsoc'15
by Sagar Ghai 16 Mar '15

16 Mar '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.

1 0

Re: [Mailman-Developers] contributing to gnu mailman development and preparing to gsoc 2015
by Abhilash Raj 16 Mar '15

16 Mar '15

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

2 1

Re: [Mailman-Developers] contributing to gnu mailman development and preparing to gsoc 2015
by Asif Saifuddin 16 Mar '15

16 Mar '15

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 <auvipy(a)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.abhilash1(a)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 >> >> >

1 0

Re: [Mailman-Developers] Contributing to GNU Mailman (GSOC '15)
by Abhilash Raj 16 Mar '15

16 Mar '15

-----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.… > > ) > > 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 OHelIx76ShcBEBWsRwVyfEwivUBZX89TX/1/FBR9xKXXURKDsr4tRCdyfGgzQKho X8ljZDJ5gd/dIQZu4mPhyi8Xf4NYv2w+XUvzPbxOGFotGPkceVc3bX19XEh/0FPU oUc4SeLBca1UcenPYboybyd3sJf3u2saqp55ToNvJ7xakVvnu6UaCmAPJORKlp1y 9n7+VbHaAtVMvv7vBnpwbBFS1XZxCHWgJay6pvk3lAc/NQozRkIWi3OpcxHvV2+V B34hU3bdMRo4BJzyRUwUaQqQr5h6FwUHliLUD8zBsvLP0WSUt/sbWu77QnMqWKCx y0DzrXJa72QCcG192WAQ0beUZ6x8SPz/UR3Lz1eU91pKZ8k/2tafOCC9TADVmwe0 +XIbaThVE3jHzjVGlsfzXkbZrw/ALIT6nqM6ZfCqRmoBGZtXqxNEgQHYNZWPM4T2 iGttIpevbymEPwld4C7s/ZRVU6lF91A+ZXPCsMB55PIY1t4Ae/p3K7ikoV23y+Pu WmcpOeqPHhYDFZgod0oabv/y3EhlU6nDDA9mNL4ofj7+uLkgIgb8/WIBV2p5HZxo OEuZQSgVtQ6saMrhgkDT =3BrY -----END PGP SIGNATURE-----

2 2