Re: [Mailman-Developers] [Queries] Related to list styles.
On Mar 13, 2015, at 01:23 PM, prakhar joshi wrote: I have some queries related to project for GSOC'15 named Improving list styles , as I have seen right now styles have been dependent on zope interface. So do we have to remove the zope dependencies ? or We have to work around to make a UI that can register the styles (that may not be a good way) , I really need what are the intentions behind that project as that will gonna help me in proceeding further for that project. Hoping for reply. There are a few different approaches one could take. Currently, you define a list of Python import paths which are used to search for styles (specifically, objects implementing the IStyle interface). These are collected in the style manager and then when a mailing list is created through the create_list() function (in app/lifecycle.py), the style name is looked up and applied to the newly created mailing list. The simplest part of this task would be to query the REST API for the available styles, and provide a selection menu for the style to apply when creating a new mailing list. This really wouldn't be enough for a GSoC though. The next step might be to add a ui for defining new styles. You'd have to work out how to store the style persistently so that it could be used later, and I'm not sure whether that would be best by writing to the database, or just creating a file on disk that can be imported into the style manager. You'd want to handle composition of styles too. All of these keep the basic idea that styles are applied when the mailing list is created, but once created a style is no longer used. We've talked about building a system where styles would be persistently associated with the mailing list so that if you change values in the style, all lists connected to that style would get updated. That would require a pretty extensive reworking of both the style system and mailing lists, so I think it would actually be *too* big for a GSoC. Cheers, -Barry ___ 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] Fast development environment setup for newbies using mmdev_bootstrap
On Mar 11, 2015, at 04:21 AM, Ankush Sharma wrote: The newbies starting to contribute to mailman sometimes face difficulty in setting up the dev environment for Mailman. Just a quick bzr hint in case folks are unaware: I create all my branches in a shared repo. This is basically a parent directory containing the .bzr subdirectory and all shared revisions. Since your branches are going to share 99% of their history, this really speeds up creating clones of the trunk. E.g.: $ cd ~/projects $ bzr init-repo mailman $ cd mailman $ bzr branch lp:mailman trunk # Now you have a `trunk` directory tracking the upstream master branch $ bzr branch trunk mywork1 $ bzr branch trunk mywork2 mywork1 and mywork2 are independent branches inside the shared repo. They get created pretty quickly because all the history is shared. Cheers, -Barry ___ 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] Discussion about Mailman plugins(GSOC 2015)
On Mar 05, 2015, at 03:09 PM, Stephen J. Turnbull wrote: I'm really having trouble with this interest in plugins as opposed to rules for chains and handlers for pipelines. To install a rule or handler is a three-step process done by the site administrator: 1. Write or download a module containing some code using a simple plugin API; the code has access to all Mailman features. 2. Save/copy the module to .../rules or .../handlers. 3. Configure the global pipeline in mailman.cfg or individual pipelines in list configurations. That looks rather pluggable to me. What does a plugin give that improves on this process? Not much, but a little. Right now you'd have to drop the module into the rules or handlers subdirectory, but that's a bit of a problem because you're conflating code provided by Mailman with custom code from the sysadmin. Think of a Linux distro package - you really don't want sysadmins messing with the source tree of Mailman. Ideally, there would be a way to add additional filesystem -- or Python import -- paths to the config files which Mailman would then search for additional rules, handlers, etc. Right now these search paths are hardcoded, e.g. mailman/core/rules.py. That's fine for finding the standard rules, but doesn't work so well for finding custom ones. This isn't a GSoC sized project on its own though. Cheers, -Barry ___ 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 2015: Seeking Information
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nakul, On Saturday 14 March 2015 05:50 AM, Nakul Gulati wrote: Hi, I am a undergraduate student pursuing Computer Science from NIIT University, Neemrana, India. Currently in my 3rd year I'm expected to graduate in summer 2016. I have experience in working on a variety of projects and have a wide skill set with skill proficiency ranging from moderate to high. The following is the link http://goo.gl/UNLshD to my resume for more information about me. After reading about mailman and going through the code base and scope of different ideas, my interest align with the project *Mailman Client written in Javascript* in particular. Hence, I'd like to pursue it as part of GSOC 2015. As you would have already read in the Ideas Page, this project requires you to implement mailman.client in Javascript with proper npm integration and test framework. You may not implement each and every API in the summer, but the production quality code and good testing framework is a must. Also, as a part of application process you'd have to fix atleast one bug in any of the mailman projects listed on the Ideas Page. In case you have doubts, you are welcome to discuss it here or on the #mailman channel on Freenode. - -- thanks, Abhilash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVA8xiAAoJEJ2bK6Bh0KZ8KY8QALesfYLgpr0Q5qRhBBYhnhcM 7PLtg23i9s0e7QTGCVthyR0Y1fEWYtnBj7l6gxGX8Mftw1/rmouWwP/sfqKCSrGb XLJZBMpiSkoLtW4MhV/AI2pnocXNx4Zr6lBJiregPYq/SxP6BP2vWHhUIkE4kSUi /1LH3IwOV+AZ87ekoPq9fydNq4wNGaqPcPmeGqRHClip9kO5bOg9TXXnl5xuvBLw SO746/Tf5DfvSubdAGCrrZzFzn2WXl/4xO7N5CmZOvDeJh18YoRBcioW/5Ye6eqP BeWKkbUFcDr1hVk2px6skq52OEAgm/Byl/llwuLpX8u8CxhAbxFKQnvbmj/5f2jK 1gK+0/a3qyfocYH2Ai04zgEuQ3qh2zGHgfamtDVeCuyuBHxpVYPY2VYPYTr3TnXI VrKSAGk5f3ATj4Oc1Qq1yFuPJNTrUjH3ucP2lr3tjPLo1UMV2ZXro96ZerpRSYFi VwPwJFUa33r0mEwMAMg+Y+9qS7hFR+SGZ00diLztnEe5MyyM2zynLLjC5Cflnz8W IpWOyJvQIyAgaipmDZ5tsCL5YxAOtuWp/QJPfEijhh6EDzTrigUVvAXEkNdkEwGb rUbtc3dCygPio27Ky+fT0fnT9Wb/2MaV2lRYXibPdsUKpamrNVF5ntqm10XAu2c4 dVzxfFJGxVtxmuzvowMz =kKI+ -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 2015: Seeking Information
Hi, I am a undergraduate student pursuing Computer Science from NIIT University, Neemrana, India. Currently in my 3rd year I'm expected to graduate in summer 2016. I have experience in working on a variety of projects and have a wide skill set with skill proficiency ranging from moderate to high. The following is the link http://goo.gl/UNLshD to my resume for more information about me. After reading about mailman and going through the code base and scope of different ideas, my interest align with the project *Mailman Client written in Javascript* in particular. Hence, I'd like to pursue it as part of GSOC 2015. I would like to discuss further about the project. Hoping for a early response. -- Regards, Nakul Gulati +91-9782477088 +91-8800539082 ___ 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] full anonymisation approach
Aside: I think if you actually use such a list you'll discover that most shy people are far more afraid of being flamed than they are of social stigma *outside* of the discussion thread. OTOH, it is likely to bring out the worst in trolls. IMHO YMMV etc. We can't overlook the fact here that shy people and most of the others facing one social stigma or other do benefit from anonymous conversations and 12-step program lays focus on such websites. Though one of the many ill-effects is that some people may get dependent on the virtual society totally avoiding confrontation from the real one as referenced in [1]. Second ill effect is that internet anonymity is more vulnerable to abuses as people don't hold any responsibility of their behaviour in such a system. Hence, internet anonymity is a double edged sword (reference [2]). The shortcomings are considerably significant but we can't overlook the advantages of using anonymity to treat such cases as the research suggests. In my opinion the requirements are: 1) Keeping list members anonymous from each other. OK, that follows from the above motivation. However, do you want the list identity to be consistent within threads, or will you assign a new list identity to a poster address for each post? Do you want list identity to be consistent across threads, or will you assign a new list identity to a poster address each time they first post to a new thread? I plan on keeping list identity of a poster constant in a thread, i.e., I generate a new list identity for a first post to a new thread. Reasons of this were mentioned by me in http://www.mail-archive.com/mailman-developers%40python.org/msg15283.html If identity is consistent within threads but not across threads, how do you determine that two posts are in different threads? For example, if post B points to post A in the References field, but the subject was changed in a significant way (ie, other than listrivia prefixes, Re: and friends, and whitespace changes that occasionally creep in due to mishandling of folding whitespace), are they in different threads? I had been following this topic on discussions list by Aanand Shekhar Roy and had also read about it online as I had realised that grouping messages in threads is a trivial necessity for my implementation. Hence we will not be relying on the subject header of a mail because of the problems you have mentioned. So, we will be using the In-Reply-To header of the mail to map the messages to their respective threads. Hence tweaking with subject will not be treated as a new thread as long as the user is using Reply-To feature, which is essential while conversating in a thread. Also using references won't be reliable as after the length of thread becomes large few entries from the references are dropped 2) Not allowing any way out for revealing any one's identity except if the user chooses to reveal it himself. That's not a reasonable requirement. It is often possible to deduce an author's identity from their choice of argument or writing style, or their employer's automatically added footer. You could argue that message content is a user choice, but I don't think many users would be happy with that point of view. I think you want to limit yourself to stuff that MUAs and MTAs put in the headers, including but not limited to originator addresses, display names, and comments. Speaking of originator, what do you propose to do about non-subscribers who are CC'd? We can remove the CC and BCC fields as if sent to a non-subscriber using CC the original id of the originator will be displayed and if a subscriber is CC'd then the mail bounces as posting address is a fake address. The originator can use one of the many available anonymous mailer services for personal anonymous mails. You might also propose removing standard signatures (ie, everything after a string matching \n-- \n). Removing other footers is much more chancy, but you could try to catch them. Yes, we can modify all footers and signatures in handlers. I'm not sure that requirements 1) - 3) are a good fit for several of your use cases, but these requirements seem like a reasonable start. I'll try to improvise on this part. Regards Rashi ___ 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] [Queries] Related to list styles.
hi, I have some queries related to project for GSOC'15 named Improving list styles , as I have seen right now styles have been dependent on zope interface. So do we have to remove the zope dependencies ? or We have to work around to make a UI that can register the styles (that may not be a good way) , I really need what are the intentions behind that project as that will gonna help me in proceeding further for that project. Hoping for reply. Thanks, Prakhar Joshi DA-IICT,Gandhinagar ___ 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
Re: [Mailman-Developers] full anonymisation approach
Sorry, I forgot to add the footnotes for the previous mail on this thread. footnotes: [1] http://counseling.caltech.edu/general/InfoandResources/Shyness [2] The Internet: Biographies (google books) Regards Rashi ___ 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] Regarding Anonymous lists
Hi, In Anonymous list project, We need to implement a strong cryptographic algorithms which encrypts the coming email address and store the encrypted code and before sending email to these lists we need to decrypt the encrypted code and then send the mail to original one. We can make use of hashsalt type techniques for password storage. Can someone acknowledge If I am right about it. Thanks Ashish Kumar ___ 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] Regarding Subscriber profile pages project
Hi, From the description, I think we need to complete following steps: 1. Create a form to take user information. 2. lists in which user want to show its user info 3. Option for user to select lists to share user info We need to add tests also for verifying each logic. Can someone please correct me If I am right about my assumptions. I have a question if there is any special interface required for list moderator or owner? Thanks Ashish Kumar ___ 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
