Mailman 3 February 2014 - Mailman-Developers

Implemented Mass Subscription via file upload
by Stephen J. Turnbull Feb. 23, 2014

Feb. 23, 2014

Rajeev S writes: > I have implemented a mass subscription via file upload feature for > Postorious which can be found here. > > https://code.launchpad.net/~rajeevs1992/mailman-rajeevs1992/trunk > > How am I to submit a merge request to the Postorious repository?I tried to > propose a merge via the launchpad, but says the branch cannot be merged. Postorius is an entirely separate project as far as Launchpad is concerned. Your URL suggests you derived from mailman, in which case Postorius and Mailman share no ancestors and the merge has to fail. If that's not it, I'll try to check the actual code later. :-) Steve

2 1

Re: [Mailman-Developers] Implemented Mass Subscription via file upload
by Mark Sapiro Feb. 23, 2014

Feb. 23, 2014

Rajeev S <rajeevs1992(a)gmail.com> wrote: > I have implemented a mass subscription via file upload feature for > Postorious which can be found here. > > https://code.launchpad.net/~rajeevs1992/mailman-rajeevs1992/trunk > > How am I to submit a merge request to the Postorious repository?I tried to > propose a merge via the launchpad, but says the branch cannot be merged. Did you propose the merge using the "Propose for merging" link on the above page? If you didn't see the link, were you logged in? On the merge proposal page did you specify the target branch as lp:postorius? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Newbie questions on mailman dev
by Stephen J. Turnbull Feb. 23, 2014

Feb. 23, 2014

Surya writes: > 1. I had created a test domain, test mailing list attached to it and few > test users. Now, I am trying to login as test users but its not > happening. Is think there might be some email validation. On a > development server, where can I hear those? With users created directly via mailman.client, there is no validation. That is a function of the front-end (Postorius), IIRC. The easiest thing to do is to create your first test user as a real account on the development server so that there are (almost :) no Internet mail issues to deal with. Then you can read mail on the same host. Your second test user can be on a free mail service or on another host you control. Having both will help you determine whether issues are due to Mailman itself or due to your MTA. When email is not being delivered, *always* report what MTA you are using. > Having said that, I had looked into the code and noticed the below > > 1. postorius.models.MailmanUser class inherits from a base class which does > not belong inherit from AbstractBaseUser of django [Django isn't > recognizing these objects as users] That's usually OK in Python. Python programs are expected to "duck type", meaning that the type of an object is determined by the available attributes and methods. Ensuring that the methods and attributes have appropriate semantics is the responsibility of the programmer. In Python, actual class inheritance is usually a convenience to avoid having to define most methods. However, typically a Mailman user object doesn't actually exist on the same host as Postorius! So a postorius.models.MailmanUser is actually an empty object which bundles a bunch of methods to extract the necessary information from a remote Mailman instance (I'm guessing, but Postorius has to be able to behave that way -- of course it could cache some information in a Django User, but that could cause problems too if the Django User were incompletely initialized). > But the method postorius.views.user.user_login() expects django User > objects to authenticate! Either the MailmanUser objects "duck type" as AbstractBaseUsers, or the necessary attributes are added elsewhere is my guess. > Is there any doc I can read to get little bit more understanding of > codebase would also be great. If there is, it would be in the src/postorius/doc/ directory. But there probably isn't. Ask here and on #mailman. And take notes :-) because when you commit them to doc/ later developers will love you forever! :-) :-) BTW, don't absolutely trust anything I say until experience proves it or Terri, Florian or Barry signs off on it. For statements about Python, Barry is the best (he's an acknowledged authority with an established title, FLUFL = Friendly Language Uncle for Life, in the Python pantheon). Terri and Florian are the authorities on Postorius itself. (I do try to mark less reliable statements with "IIRC" and the like, but I'm not perfect.) Steve

1 0

Implemented Mass Subscription via file upload
by Rajeev S Feb. 22, 2014

Feb. 22, 2014

Hi, I have implemented a mass subscription via file upload feature for Postorious which can be found here. https://code.launchpad.net/~rajeevs1992/mailman-rajeevs1992/trunk How am I to submit a merge request to the Postorious repository?I tried to propose a merge via the launchpad, but says the branch cannot be merged. What am I doing wrong? *Regards,Rajeev S* *Government Engineering College,Thrissur* *http://rajeevs.tk <http://rajeevs.tk>*

1 0

Newbie questions on mailman dev
by Surya Feb. 22, 2014

Feb. 22, 2014

Hello there, I am Surya trying to get my hands dirty with Mailman, solve some bugs - The idea is to get familiar with codebase! For now, I thought to start with Postorius. I had successfully setup mailman development environment; Just have few newbie questions. I appreciate if someone can help me on them and possibly give a direction too! 1. I had created a test domain, test mailing list attached to it and few test users Now, I am trying to login as test users but its not happening. Is think there might be some email validation. On a development server, where can I hear those? Having said that, I had looked into the code and noticed the below 1. postorius.models.MailmanUser class inherits from a base class which does not belong inherit from AbstractBaseUser of django [Django isn't recognizing these objects as users] But the method postorius.views.user.user_login() expects django User objects to authenticate! I am a bit confused here. Is there any doc I can read to get little bit more understanding of codebase would also be great. Thanks Surya

1 0

Gsoc idea discussions : Continuous integration tool
by Varun Sharma Feb. 22, 2014

Feb. 22, 2014

Hi all, I am interested in continuous integration tool as my gsoc project and would like to discuss further it's possible implementations. I think one possible implementation for gatekeeper is : Making another django project mm_gatekeeper which every developer must run in order to commit to trunk. We can host its repo of on launchpad. It will act as a proxy to bzr and will perform bzr commit only after all the unit and doc tests succeeds. bzr pull can be implemented as $ mm_gatekeeper PROJECT_NAME pull or to pull all projects $ mm_gatekeeper pull Instead of using bzr commit in postorius we can use $ mm_gatekeepar PROJECT_NAME COMMAND $ mm_gatekeeper postorius commit -m"commit message" commit command will run all the tests first and then using python subprocess execute the bzr commit command. We can import all the unit tests from every project while implementing commit command and every test can be given a value so that we can check if total number of tests passed is equal to total tests written. It can be further expanded in django by saving commiter's history, adding automatic testing schedules, getting the branch info etc.

1 0

Re: [Mailman-Developers] Continuous integration tool for the Mailman suite
by Barry Warsaw Feb. 21, 2014

Feb. 21, 2014

Welcome Shubham and Emily (and all prospective GSoC students). On Feb 20, 2014, at 08:48 AM, Emily Dunham wrote: >You're on the right track by getting into IRC and posting on the mailing >list! On IRC, it helps to ask a specific question and then wait about 8 >hours for a reply, since the developers are in a wide variety of different >time zones. You can always ping me or one of the other core developers in IRC. I'm usually around during US/Eastern normal working hours, but I don't always pay background attention to the channel. Cheers, -Barry

1 0

Re: [Mailman-Developers] [Mailman-Users] MM 3 and OSCON 2014
by Barry Warsaw Feb. 21, 2014

Feb. 21, 2014

On Feb 21, 2014, at 08:15 AM, Mark Sapiro wrote: >> 2. Is MM going to have a presence at O'reilly's OSCON 2014 in July? > >I don't plan to be there, but others may. There will be a number of us >at PyCon in April <https://us.pycon.org/2014/>. I won't be at OSCON either. We'll be sprinting on Mailman 3.0 at Pycon. I want to emphasize two things at the sprint: working on Postorius and Hyperkitty, and porting MM3 to Python 3. But we can work on other things if you have an interest. AFAICT, the sprint page is not up yet though. Please come and join us! -Barry

1 0

Kernel update breaks Mailman!!
by Lindsay Haisley Feb. 20, 2014

Feb. 20, 2014

I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA, running Python 2.7.3. I track security updates and install them promptly when they're issued by Ubuntu. Yesterday I updated the Linux kernel from 3.2.0-58-generic (x86_64) to 3.2.0-59-generic and Mailman quit working. List posts made it through to the archives, and were apparently queued within Mailman, but wouldn't go out. The mail server was working OK for non-list email. Today I backed out the kernel update and posts to lists sent yesterday and today are going out without problems. I can find nothing in the Mailman logs, or in the mail server logs, indicating a problem. This is the first time I've ever had a problem with a server kernel update breaking something related to mail. Has anyone else seen this problem? Does anyone have any insight into how to address it? -- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |

3 3

Re: [Mailman-Developers] Continuous integration tool for the Mailman suite
by Emily Dunham Feb. 20, 2014

Feb. 20, 2014

Shubham, You're on the right track by getting into IRC and posting on the mailing list! On IRC, it helps to ask a specific question and then wait about 8 hours for a reply, since the developers are in a wide variety of different time zones. Congratulations on getting the Vagrant VM set up already! I've found that that process can be anywhere from easy to infuriating, depending on your host system's configuation. With that up and running, here's what I'd do next: 1) If you're not already familiar with the Bazaar and Launchpad development workflow, read up on it at http://wiki.list.org/display/DEV/MailmanOnLaunchpad and http://wiki.list.org/display/DEV/MailmanBranches to get familiar with the bzr workflow and make sure you're making your changes on the correct branch. 2) Look through the Mailman issue tracker at https://bugs.launchpad.net/mailman and find simple bugs that you can confirm and then write tests for. Communicate with the people who have submitted and worked on the bugs you're looking at, to make sure your tests capture them correctly. 3) Write those tests, while studying Python best practices for testing and the conventions of Mailman's existing tests. 4) Research the similarities and differences between various Continuous Integration tools and ask questions on the list and in IRC to determine how Mailman's testing needs correlate to the tools' strengths and weaknesses. Good luck, have fun, and come here or the IRC channel if you have any problems getting things set up! --Emily Dunham Also a prospective GSOC student, interested in CI and command-line tool projects On Thu, Feb 20, 2014 at 4:17 AM, Shubham Somani <shubhamsomani92(a)gmail.com>wrote: > Hi, > > My Name is Shubham Somani. I am a final year student at Delhi College of > Engineering. I am a successful Google Summer of Code 2013 student. > > I wish to participate in this year's Google Summer of Code with Mailman. > > Creating a continuous integration tool for the Mailman suite seemed like an > interesting project to me and I have built Mailman's code with Vagrant and > Chef. > > I would be very glad if some one could provide me pointers of what to do > next to contribute to this project. > > Thanks! > Shubham > _______________________________________________ > 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/dunhame%40onid.o… > > Security Policy: http://wiki.list.org/x/QIA9 >

1 0