Mailman 3 May 2014 - Mailman-Developers

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Barry Warsaw 03 May '14

03 May '14

On May 03, 2014, at 09:59 AM, Tom Browder wrote: >Using the latest cli commands as shown in Rajeev's >/src/mailmanclient/cli/docs/using.txt would be for the "default" list >style: > > test_one = example.create_list('test-one') > >Then, for other styles, we could use something like (pardon my pseudo code): > > test_one = example.create_list('test-one', style='read-only') > >Looking briefly at the cli code I see nothing about the list >attributes Barry mentioned in last year's thread referenced above, so >I'm not sure how this would all fit together, but I think it needs to >be considered. Using MM3's internal API: from mailman.app.lifecycle import create_list mylist = create_list('test(a)example.com', style='legacy-announce') Using the REST API http://pythonhosted.org//mailman/src/mailman/rest/docs/lists.html#apply-a-s… The CLI (i.e. `mailman create` command) does not yet accept a --style argument, but that would be pretty trivial to add. Note that currently only the legacy-default and legacy-announce styles are defined by default. Cheers, -Barry

2 1

Re: [Mailman-Developers] ANNOUNCE: The GNU Mailman 3 suite, beta 1 preview
by Mark Sapiro 03 May '14

03 May '14

On 05/03/2014 07:15 AM, Tom Browder wrote: > On Thu, Apr 24, 2014 at 9:19 AM, Barry Warsaw <barry(a)list.org> wrote: > ... >> On behalf of the Mailman development team, I am happy >> to announce the first beta release of the full Mailman 3 suite. >> >> This release includes: > ... >> Core >> project - https://launchpad.net/mailman > ... > > I apologize for my confusion, but I'm not used to the bazaar model for > multiple developers. I'm used to the svn model for C/C++ code where > we keep the trunk as the latest development version (but we keep the > trunk so it always builds without error). > > If I want the latest development version of Mailman should I use the > announced lp address above or the one I'm using now: > > Related branches: > parent branch: http://bazaar.launchpad.net/~mailman-coders/mailman/3.0/ > revision-id: barry(a)list.org-20140101145942-b9vqi0xmcewpk4mb > date: 2014-01-01 09:59:42 -0500 > build-date: 2014-05-03 10:07:35 -0400 > revno: 7232 Now I'm confused, but it looks like you are looking at a local (to you) branch that you branched at rev 7232 from lp:mailman or http://bazaar.launchpad.net/~mailman-coders/mailman/3.0/ or some other alias for that branch. If you now cd to that branch on your local machine and do 'bzr pull' it should bring you up to the head of the branch on launchpad at rev 7251. OTOH, if that is not your local branch, but a branch you obtained elsewhere, then you probably should not be using it as the 'official' branch is lp:mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Stephen J. Turnbull 03 May '14

03 May '14

Tom Browder writes: > I haven't watched this entire thread, but I hope someone is > considering setting appropriate defaults for at least two mailing list > types such as: > > read-only (news) > read-post (moderated or not) Not in that terminology, no. What do you hope to type, and what effect do you want it to have?

2 1

ANNOUNCE: The GNU Mailman 3 suite, beta 1 preview
by Barry Warsaw 03 May '14

03 May '14

Hello Mailman enthusiasts! Time and motion Wind and sun and rain Days connect like boxcars in a train Another Pycon has come and gone and with it, another fantastic sprint among the core developers. We accomplished quite a bit, and now we'd like to share the results with you. On behalf of the Mailman development team, I am happy to announce the first beta release of the full Mailman 3 suite. This release includes: * Postorius 1.0.0b1 (Year of the Parrot), our new Django-based web user interface for list owners and list members. * HyperKitty 1.0.0b1, the fantastic new Django-based archiver. * Mailman Core 3.0b4 (Time and Motion), the mailing list engine and administrative REST API. * The mailman-bundler package 3.0b1, a helpful buildout-based tool for putting it all together. We're very excited to finally be able to announce this preview of the entire suite of tools, and we hope you'll give it a try. As with any beta software, we give a word of caution should you be adventurous enough to want to try it in production. There are surely bugs and missing features, but we feel confident enough to encourage you to play with the system and provide us with feedback, bug reports, suggestions, and above all, contributions! Each project is separately downloadable from the Python Cheeseshop, and links are provided below. Perhaps the best way to begin is to grab the bundler, unpack it and, follow the directions included in the bundle. It should work on most modern *nixes with Python 2.7. You can download the bundler tarball from: https://pypi.python.org/pypi/mailman-bundler/3.0b1 See below for links to the individual project pages, bug report packages, and package documentation. The best place to discuss Mailman 3 is on the mailman-developers mailing list, or on IRC via the freenode #mailman channel. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) P.S. My personal, deepest thanks to Florian, Terri, Aurélien, Mark, John, and Piotr for coming to Pycon, working hard and joyfully at the sprints, sharing friendly meals and tea shop excursions, and to Steve who wasn't able to make it in person, and also to all the contributors to the project who make the code better and the community an honor to be a part of. Postorius project - https://launchpad.net/postorius bugs - https://bugs.launchpad.net/postorius download - https://pypi.python.org/pypi/postorius/1.0.0b1 docs - http://pythonhosted.org//postorius/ HyperKitty project - https://fedorahosted.org/hyperkitty/ bugs - https://fedorahosted.org/hyperkitty/report download - https://pypi.python.org/pypi/HyperKitty/1.0 docs - https://hyperkitty.readthedocs.org/en/latest/ Core project - https://launchpad.net/mailman bugs - https://bugs.launchpad.net/mailman/+bugs?field.tag=mailman3 download - https://pypi.python.org/pypi/mailman/3.0.0b4 docs - http://pythonhosted.org/mailman/ Bundler project - https://launchpad.net/mailman-bundler bugs - https://bugs.launchpad.net/mailman-bundler download - https://pypi.python.org/pypi/mailman-bundler/3.0b1 docs - README.rst (in the unpacked tarball)

2 1

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Stephen J. Turnbull 03 May '14

03 May '14

Rajeev S writes: > Hi, > > I have added two more methods, *create domain* and *list mailing lists*. > The listing feature is performed using the `tabulate` module, which I have > added to the install_requires. > > Also, the usage of the CLI is explained in the cli/docs/using.txt. Great! I have $DAYJOB stuff that will prevent me from reviewing until at least Monday evening (Japan time), but thank you for posting and keeping all of us updated.

1 0

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Tom Browder 03 May '14

03 May '14

On Sat, May 3, 2014 at 2:49 AM, Rajeev S <rajeevs1992(a)gmail.com> wrote: > Hi, > > I have added two more methods, *create domain* and *list mailing lists*. I haven't watched this entire thread, but I hope someone is considering setting appropriate defaults for at least two mailing list types such as: read-only (news) read-post (moderated or not) Excuse my imprecise terminology. Best regards, -Tom

1 0

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Rajeev S 03 May '14

03 May '14

Hi, I have added two more methods, *create domain* and *list mailing lists*. The listing feature is performed using the `tabulate` module, which I have added to the install_requires. Also, the usage of the CLI is explained in the cli/docs/using.txt. *Regards,Rajeev S* *Government Engineering College,Thrissur* *http://rajeevs.tk <http://rajeevs.tk>* On Fri, May 2, 2014 at 9:06 PM, Rajeev S <rajeevs1992(a)gmail.com> wrote: > Hi, > > I have added the licensing blocks to the files and pushed the code. > > > *Regards,Rajeev S* > *Government Engineering College,Thrissur* > *http://rajeevs.tk <http://rajeevs.tk>* > > > On Fri, May 2, 2014 at 7:13 AM, Barry Warsaw <barry(a)list.org> wrote: > >> On May 02, 2014, at 06:36 AM, Rajeev S wrote: >> >> >3.The code has been verified with pep8 *and* flake8 tools. It also passes >> >most of the guidelines mentioned in Barry's styleguide. Some of the >> >guidelines are yet to be met, like the licensing block >> >and stuff like __all__. Also the ^L at major sections are also not >> >added.(Is it still necessary?) >> >> Files should definitely all have licensing blocks. ^Ls are not required. >> I >> find them useful for Emacs navigation, but I understand they may be >> distracting for other folks in other editors. I really need to update the >> style guide for Python 3 and not-quite-Python-3-yet. >> >> -Barry >> _______________________________________________ >> 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/rajeevs1992%40gm… >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > >

1 0

Re: [Mailman-Developers] [GSoC 2014] Mailman CLI Project
by Barry Warsaw 02 May '14

02 May '14

On May 02, 2014, at 06:36 AM, Rajeev S wrote: >3.The code has been verified with pep8 *and* flake8 tools. It also passes >most of the guidelines mentioned in Barry's styleguide. Some of the >guidelines are yet to be met, like the licensing block >and stuff like __all__. Also the ^L at major sections are also not >added.(Is it still necessary?) Files should definitely all have licensing blocks. ^Ls are not required. I find them useful for Emacs navigation, but I understand they may be distracting for other folks in other editors. I really need to update the style guide for Python 3 and not-quite-Python-3-yet. -Barry

2 1

[GSoC 2014] Mailman CLI Project
by Rajeev S 02 May '14

02 May '14

Hi, I will be using the following branch for the Mailman CLI project *https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli <https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli>* I have created and committed the basic structure of the project in the branch.Also, as the first step I have implemented the "create list" functionality for the command line tools. A few snapshots: 1.As discussed in stage of proposal review, the command mmclient (currently script) triggers the shell if no argument is specified and performs the action when an argument is supplied. 2.The argparse module has been used for parsing arguments. Shell is built using Cmd module, currently no functionality. 3.The code has been verified with pep8 *and* flake8 tools. It also passes most of the guidelines mentioned in Barry's styleguide. Some of the guidelines are yet to be met, like the licensing block and stuff like __all__. Also the ^L at major sections are also not added.(Is it still necessary?) 4.The code rests in mailman.client/src/mailmanclient/cli I guess it would be easier to discuss the design and architecture based on this. *Regards,* *Rajeev S* *Government Engineering College,Thrissur* *http://rajeevs.tk <http://rajeevs.tk>*

1 0

Re: [Mailman-Developers] GSOC 2014: CI tool for the Mailman suite and postorius improvements
by Barry Warsaw 01 May '14

01 May '14

Hi Varun, welcome to Mailman GSoC! On Apr 30, 2014, at 12:24 PM, varun sharma wrote: >Thanks for giving me opportunity to work with mailman community this >summer. I'm an undergraduate student from Manipal Institute Of Technology, >India and i'll be working on project "CI tool for the Mailman suite and >postorius improvements". >I would love to get feedback and suggestions from the community regarding >my project which involves: >1. CI tool for Mailman Suite (mailman core, postorius, hyperkitty) >2. The UI Testing Framework for Postorius >I am in process of discussing the best possible implementation for this >project with my mentors and advice from the community for the same will be >very helpful. One of the things I think is critical for the core, is testing it against supported the two supported db backends, SQLite and PostgreSQL. Eventually others if/when we get some contributions. I'd also love to see some testing against the major MTAs, and on other *nix platforms other than Ubuntu and Debian. Cheers, -Barry

2 2