Re: [Mailman-Developers] bugs on launchpad
My idea as a user would be to be able to select from my web configuration page an option: send_public_url_in_mail_footers: [ disabled, gmane_url, mailmanweb_url ] And maybe it would be cool (if possible I have no idea) to add a mail command that when I send subject: public $mailing_list $id I get back an email with this url. Because maybe from one mailing list I'm normally not interested in the url and I also want it in some cases. Not sure I anyone else in the world would like this feature though :D ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On 3/22/2012 5:48 PM, Stephen J. Turnbull wrote: On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw ba...@list.org wrote: If we add something like $archive_url to the decoration interpolation dictionary, what happens when we have multiple archivers that support permalink() enabled? Do we chose one at random (these are unordered)? -1 I agree so -2. I thinking is if you list administrator/owner has not defined an order, make it simple and impose a known order in that case - alphabetize/sort the order and pick the first one. Do we add a configuration variable to select a primary archiver for this? +1 +2 This would allow the list administrator/owner to define and pick the primary archiver. For any other archivers, people can go to the Archived-At header(s). If there's *no* archiver configuration variable, we don't know where to point to anyway for Gmane-like archivers (yes, I know, catering to Gmane will give Brad hives, but some people like Gmane). The local archive, if it exists, may seem TOOWTDI, but it might not be the preferred one even if it's the only one configured in Mailman (although that seems a lot less likely than the case where somebody just grandfathers an existing Gmane subscription as the archive URL of choice). Do we allow something like $archive_url.prototype as an interpolation variable to select e.g. the 'prototype' archiver? -1 Too complex. If people want alternative archives, they can go to the list FAQ or the Archived-At headers. If we go this way, we'd better have a *really* good comment and a pre-existing entry in the FAQ to save Mark some time. :-) I agree with Stephen. Too complex and can be confusing without it being well documented with a number of examples. ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] python 3
Someone told me that I should poke Barry about Python3 support, so here I am ;) It's clearly something that can be done really soon, but I think it's worth to start thinking about it. In particular I noticed that lazr.config have been untouched since 2009, which makes me think that is less likely that they will be ported to Python 3. Is it a valid assumption or there is a porting plan? Are there any other blocking factors in general from libraries or other issues?? ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] GSoC 2012
Hi Everyone, I am Vikash and very much interested in contributing to mailman and being a GSoC student this year. So far, I have successfully installed mailman in my system. I do have skills in Python 2.7 but as I am very new to mailman thus I am looking for something small to hack and doable in this summer. Also, the idea page doesnot mention the skills required for the project so its somewhat difficult for me to choose one. As a result I would like you to guide me over the same . I am willing to learn a lot this summer :-) Regards Vikash Agrawal -- sent via HTC Sensation ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] python 3
On Mar 23, 2012, at 08:19 PM, Andrea Crotti wrote: Someone told me that I should poke Barry about Python3 support, so here I am ;) It's clearly something that can be done really soon, but I think it's worth to start thinking about it. Probably you meant s/can/can't/ ... but still, it may not be so dire. It won't happen for Mailman 3.0 but I think it should definitely be a goal for Mailman 3.1 (which will *not* take another 4 years :). I've tried to be very careful in writing Mailman 3 so that *its* code should be relatively easy to port to Python 3. No doubt there will be gotchas, but I am definitely keeping that in mind as I go. In particular I noticed that lazr.config have been untouched since 2009, which makes me think that is less likely that they will be ported to Python 3. Is it a valid assumption or there is a porting plan? Are there any other blocking factors in general from libraries or other issues?? Really, we need to get our dependency stack ported. I'm committed to making Mailman 3 a Python 3 application as soon as it's possible. Martin von Loewis was working on porting Storm at Pycon, which obviously is a critical component, but I don't think he quite finished. We need restish.io ported, along with its dependency stack, as well as several of the still-unported Zope libraries, and *their* dependency stacks. By looking in buildout's eggs directory, you can get a good sense of what is currently required: flufl.bounce-2.1-py2.7.egg/ flufl.enum-3.3.1-py2.7.egg/ flufl.i18n-1.1-py2.7.egg/ flufl.lock-2.2-py2.7.egg/ flufl.password-1.2-py2.7.egg/ httplib2-0.7.4-py2.7.egg/ lazr.config-1.1.3-py2.7.egg/ lazr.delegates-1.2.0-py2.7.egg/ lazr.smtptest-1.3-py2.7.egg/ mimeparse-0.1.3-py2.7.egg/ restish-0.12.1-py2.7.egg/ setuptools-0.6c12dev_r88846-py2.7.egg/ six-1.1.0-py2.7.egg/ storm-0.19-py2.7-linux-x86_64.egg/ WebOb-1.2b3-py2.7.egg/ z3c.recipe.scripts-1.0.1-py2.7.egg/ z3c.recipe.tag-0.4.1-py2.7.egg/ zc.buildout-1.5.2-py2.7.egg/ zc.recipe.egg-1.3.2-py2.7.egg/ zc.recipe.testrunner-1.4.0-py2.7.egg/ zope.component-3.12.0-py2.7.egg/ zope.configuration-3.8.0-py2.7.egg/ zope.event-3.5.1-py2.7.egg/ zope.exceptions-3.6.1-py2.7.egg/ zope.i18nmessageid-3.6.1-py2.7-linux-x86_64.egg/ zope.interface-3.8.0-py2.7-linux-x86_64.egg/ zope.schema-4.0.1-py2.7.egg/ zope.testing-3.10.3-py2.7.egg/ zope.testrunner-4.0.4-py2.7.egg/ The flufl packages are of course ported. :) Not all of that will be needed. For example, I do want to eventually get rid of zc.buildout, zope.testing, and zope.testrunner, so some of those dependencies will go away as a result of that. The best way to help is to work with those upstreams to get official Python 3 support in their libraries. If you're looking for guidance, start with storm, WebOb, restish, lazr.*, and the unported zope.* libraries (minus .testing and .testrunner, and possibly .i18nmessageid). The email6 package availability will probably help us a lot too. Help R. David Murray on that package, or just pay him money to finish it. :) Cheers, -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
Hello Mailman enthusiasts! Use the key, unlock the door See what your fate might have in store... Building on the excitement and amazing progress at our sprints at Pycon 2012, I am very happy to announce the availability of GNU Mailman 3.0 beta 1, code named The Twilight Zone. After nearly four years of design, discussion, and development, we can now see a clear path to a final release. I thank everyone who has helped us get here, by participating on the mailman-developers mailing list, the bug tracker, in private conversations, and code contributions, both to Mailman itself and all the great projects it builds on. Special thanks go to our recent sprinters, Andrea Crotti, Florian Fuchs, Toshio Kuratomi, Daniel Mizyrycki, Terri Oda, Mark Sapiro, and Stephen Turnbull. While you do want to be careful using 3.0b1 in production, I hope that you will get a copy of the code and run it through its paces. Several people are known to be running real mailing lists using the code base. At this point, the feature set is frozen, as is the database schema. We'll use the schema migration machinery to do any schema changes from here to the final release. I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. Postorius is in large part based on the great work of Anna Senarclens de Grancy and Benedict Stein who worked on a new Mailman web ui during their Google Summer of Code projects in 2010 and 2011. This alpha version connects to Mailman 3.0's REST API to add and edit lists and domains, as well as to moderate messages. It uses Django's auth app and Mozilla's BrowserID for authentication (a list of the current features is contained in the NEWS file of the package). Apart from the current state there are many more ideas left for the upcoming releases. There is a great team working on the web ui as well as on a new archiver, so stay tuned, and come join us! You can download GNU Mailman 3.0b1 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman Postorius 1.0a1 is available from Launchpad and Cheeseshop as well: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius The GNU Mailman documentation is available online at: http://packages.python.org/mailman/ You can submit bug reports to GNU Mailman and Postorius at: https://bugs.launchpad.net/mailman https://bugs.launchpad.net/postorius GNU Mailman and Postorius are released under the GNU General Public License version 3 or later. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On Mar 23, 2012, at 9:00 PM, Barry Warsaw ba...@list.org wrote: Use the key, unlock the door See what your fate might have in store... Everybody walk the dinosaur! Seriously though, this is amazing news! Thanks to everyone who helped work on this. I can't wait to give it a try! Cheers, Justin ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
No INSTALL file in the tarball? For folks like me who aren’t savvy with Python’s installers and were expecting to find configure/make, it would help a great deal. This may be the wrong list for this, but just in case I stumbled on the right way to install it, I got this when doing sudo python setup.py install: --- Processing dependencies for mailman==3.0.0b1 error: Installed distribution zope.interface 3.5.1 conflicts with requirement zope.interface=3.8.0 --- -FG On 23.3.12 9:00 PM, Barry Warsaw wrote: Hello Mailman enthusiasts! Use the key, unlock the door See what your fate might have in store... Building on the excitement and amazing progress at our sprints at Pycon 2012, I am very happy to announce the availability of GNU Mailman 3.0 beta 1, code named The Twilight Zone. After nearly four years of design, discussion, and development, we can now see a clear path to a final release. I thank everyone who has helped us get here, by participating on the mailman-developers mailing list, the bug tracker, in private conversations, and code contributions, both to Mailman itself and all the great projects it builds on. Special thanks go to our recent sprinters, Andrea Crotti, Florian Fuchs, Toshio Kuratomi, Daniel Mizyrycki, Terri Oda, Mark Sapiro, and Stephen Turnbull. While you do want to be careful using 3.0b1 in production, I hope that you will get a copy of the code and run it through its paces. Several people are known to be running real mailing lists using the code base. At this point, the feature set is frozen, as is the database schema. We'll use the schema migration machinery to do any schema changes from here to the final release. I'm also ecstatic to announce the first alpha release of Postorius, our new official name for the Django-based Mailman 3 web user interface. The name was suggested by core developer Florian Fuchs in honor of a bass hero of both of ours, Jaco Pastorius. Postorius 1.0 alpha 1 is code named Space Farm. Postorius is in large part based on the great work of Anna Senarclens de Grancy and Benedict Stein who worked on a new Mailman web ui during their Google Summer of Code projects in 2010 and 2011. This alpha version connects to Mailman 3.0's REST API to add and edit lists and domains, as well as to moderate messages. It uses Django's auth app and Mozilla's BrowserID for authentication (a list of the current features is contained in the NEWS file of the package). Apart from the current state there are many more ideas left for the upcoming releases. There is a great team working on the web ui as well as on a new archiver, so stay tuned, and come join us! You can download GNU Mailman 3.0b1 from Launchpad or the Python Cheeseshop: https://launchpad.net/mailman http://pypi.python.org/pypi/mailman Postorius 1.0a1 is available from Launchpad and Cheeseshop as well: https://launchpad.net/postorius http://pypi.python.org/pypi/postorius The GNU Mailman documentation is available online at: http://packages.python.org/mailman/ You can submit bug reports to GNU Mailman and Postorius at: https://bugs.launchpad.net/mailman https://bugs.launchpad.net/postorius GNU Mailman and Postorius are released under the GNU General Public License version 3 or later. Enjoy! -Barry (On behalf of the entire GNU Mailman development team) ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/felipe%40felipegasper.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
