Re: [Mailman-Developers] RELEASED: GNU Mailman 3.0 beta 1 and Postorius 1.0 alpha 1
On 03/24/2012 02:00 AM, 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) Great news Barry, but just one thing, I checked now on list.org and the GNU Mailman website and there is no mention of this release.. is that on purpose? ___ 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
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
[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
Re: [Mailman-Developers] Killing off Pipermail and the effects on scrubbing in Mailman 3
On 03/19/2012 09:14 PM, Mark Sapiro wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/19/2012 4:25 AM, Barry Warsaw wrote: There are lots of options here. As mentioned, virtualbox should be a good option, and you can probably use something like wubi to create an Ubuntu desktop running along side Windows. Thanks to all for the advice. I have some learning to do. I actually have VirtualBox installed and for the sprint I had a Vagrant VM set up running the basic http://files.vagrantup.com/lucid32.box. I had set up a virtualenv on this box with Sphinx installed for the Sphinx tutorial at PyCon, and this worked really well. When I got to the Mailman sprint, I tried to install MM 3 on this Vagrant VM, and I ran into some error with buildout trying to compile some package and failing with a missing Python.h file. I ran 'sudo apt-get install python-dev' on the VM which I thought would fix it, and the install seemed to run OK, but I still had no Python.h. At that point, I gave up and went to a virtualenv on my production server. At this point, I don't know whether the best approach is look for a more complete development box for Vagrant or figure out how to provision the basic Vagrant box with what I need or forget Vagrant and install directly in VirtualBox or go with a dual-boot. Anyway, it's going to be interesting to figure this out. Since I was curious to see I created a vagrant VM with lucid and I only needed to install the following: To install (Lucid32): - python - python-dev - bzr - python-setuptools - gcc To make everything work and be able to run buildout and bin/test in mailman bzr version. So now I was thinking to transform this manual steps in a Vagrantfile, and we could use this to ship for people that want to try, other things to do: Optional packages: - Gnome / XFCE / Other - vim To check/set: - launchpad login, possibly passing the authentication and the SSH key somehow to the vagrant file - dimension of the VM to make sure it's not too small PS. I get 6 failures running the tests though, as File /home/vagrant/mailman/src/mailman/model/docs/users.rst, line 172, in users.rst Failed example: user_2.preferred_address = anne Differences (ndiff with -expected +actual): Traceback (most recent call last): - ... - UnverifiedAddressError: Anne Person a...@example.com + File /usr/lib/python2.6/doctest.py, line 1248, in __run + compileflags, 1) in test.globs + File doctest users.rst[41], line 1, in module + user_2.preferred_address = anne + File /home/vagrant/mailman/src/mailman/model/user.py, line 112, in preferred_address + raise UnverifiedAddressError(address) + UnverifiedAddressError: unprintable UnverifiedAddressError object ___ 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] VM for Mailman development
On 03/19/2012 11:02 PM, Terri Oda wrote: On 03/19/2012 03:14 PM, Mark Sapiro wrote: At this point, I don't know whether the best approach is look for a more complete development box for Vagrant or figure out how to provision the basic Vagrant box with what I need or forget Vagrant and install directly in VirtualBox or go with a dual-boot. Anyway, it's going to be interesting to figure this out. Incidentally, how much interest would there be in having a Mailman-developer VM (say, for VirtualBox) around and easy to download? Some modern distro, appropriate dev tools, and a checkout of moderately recent code, maybe even ready to run with instructions on the desktop or something? It seems like it might be a nice thing to hand out to prospective GSoC students as well as Mark. ;) The Systers folk made one a few years ago for 2.1 dev and maybe it's time for an updated version? Terri That sounds like a good idea :) In this case, maybe something declarative with puppet/vagrant might really be a very good idea, since it's much easier to ship a configuration file and it has to be deployed / updated easily... ___ 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] Killing off Pipermail and the effects on scrubbing in Mailman 3
On 03/19/2012 11:25 AM, Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mar 17, 2012, at 04:43 PM, Mark Sapiro wrote: Next step for me may be to learn more about how the unittests fit within their framework so I can create some. It's *relatively* simple. Essentially all unittests live in a test_foo.py module inside a tests/ directory (which has an __init__.py so it's a package). I generally name unittest.TestCase subclasses as TestFoo and individual tests inside there as test_foo() methods. There are lots of examples spread throughout. It's only a little extra work if you have to create a new tests/ subdirectory or test_foo.py module, but again, it should be pretty straightforward. These all get auto-discovered by the zope.testing framework, so there's nothing else necessary to hook it all up. The one other tricky thing is the layers, which are a zope.testing mechanism to share more generic resources among a suite of tests. E.g. if you need the rest server to be started, you'd use the RESTLayer (see mailman.testing.layers for what's currently defined). To enable a layer, you just need to set the `layer` attribute of the TestFoo class. Almost all the tests will require at least the ConfigLayer since that brings up the Zope component architecture, connfiguration system, etc. zope.testing is a bit weird here because the normal rules of subclasses don't actually apply. E.g. the LMTPLayer derives from ConfigLayer which derives from MockAndMonkeyLayer. All the appropriate setUp()s get called by zope.testing so you don't need to up-call explicitly in the layer class. Yes, this kind of sucks since it's magical, and it's one reason why eventually I'd like to switch to something like testresources and a more sane testing framework, but that's a lot of effort for little immediate value. Note that doctests are all set up in test_documentation.py so they're not really all that special. Just as a suggestion, it would be nice to have a few lines in the documentation about this, something like you just explained would be already quite good, since it's not so clear by just looking at the code.. Cheers, Andrea ___ 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] Killing off Pipermail and the effects on scrubbing in Mailman 3
On 03/19/2012 12:27 PM, Barry Warsaw wrote: On Mar 19, 2012, at 12:03 PM, Andrea Crotti wrote: Just as a suggestion, it would be nice to have a few lines in the documentation about this, something like you just explained would be already quite good, since it's not so clear by just looking at the code.. Care to adapt my post into a merge proposal? :) -Barry Yes sure I will do that ASAP.. ___ 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] Killing off Pipermail and the effects on scrubbing in Mailman 3
On 03/19/2012 09:14 PM, Mark Sapiro wrote: Thanks to all for the advice. I have some learning to do. I actually have VirtualBox installed and for the sprint I had a Vagrant VM set up running the basic http://files.vagrantup.com/lucid32.box. I had set up a virtualenv on this box with Sphinx installed for the Sphinx tutorial at PyCon, and this worked really well. When I got to the Mailman sprint, I tried to install MM 3 on this Vagrant VM, and I ran into some error with buildout trying to compile some package and failing with a missing Python.h file. I ran 'sudo apt-get install python-dev' on the VM which I thought would fix it, and the install seemed to run OK, but I still had no Python.h. At that point, I gave up and went to a virtualenv on my production server. At this point, I don't know whether the best approach is look for a more complete development box for Vagrant or figure out how to provision the basic Vagrant box with what I need or forget Vagrant and install directly in VirtualBox or go with a dual-boot. Anyway, it's going to be interesting to figure this out. Well but why using Vagrant? Vagrant is great to create VMS for automatic testing, but if you want to create your own VM with all your things that you need I don't see how it can help, just install a normal Ubuntu/whatever on Virtualbox and you're fine.. And another possible advice is to always copy the errors you get, also because most of the times you can get the answer you want simply by a quick google search ;) ___ 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] Killing off Pipermail and the effects on scrubbing in Mailman 3
On 03/17/2012 11:43 PM, Mark Sapiro wrote: Also, I need to figure out a better development platform for Windows boxes. I had a perfect opportunity to scrap Windows all together when I had to recover from a hard drive crash on my main development box last year, but the dice fell the wrong way on that one. Anyway, Cygwin is not going to cut it for MM 3. At the sprint, I tried installing MM 3 in a vagrant VM, but there was too much missing (e.g., no Python.h) and even 'apt-get install python-dev' didn't fix that. I ended up working remotely inside a virtualenv on my production server. That actually seems to work OK, but I'm afraid that as I get deeper into it, there will be things I need to do that I won't want to do on my production box. Anyway, if anyone has any suggestions for me besides the obvious bite the bullet now and scrap Windows - it will only be worse later, I'm interested. I suppose I could always dual-boot Windows and some Linux side by side. Maybe I can organize a sprint at the next PyCon - Migrating to Linux and killing Windows one PC at a time. I would definitively suggest to get rid of Windows, but if you don't want or can't do the big step there is no reason to do a dual-boot, a just create a Linux virtual machine and you're done :) Unless you don't have much RAM is the best solution, and there are even pre-made virtual machines here: http://virtualboximages.com/ so it doesn't really take long to set up something working :) ___ 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] programming languages
I just noticed that on the launchpad page the programming languages appears: Programming Languages: Python, C but I don't see any trace of C... Cheers, Andrea ___ 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] bugs on launchpad
Hi everyone, I filed in two bugs today: https://bugs.launchpad.net/mailman/+bug/956889 https://bugs.launchpad.net/mailman/+bug/956384 because I thought we could have a discussion there about these topics. But now I was wondering if it is a good idea, is it maybe better to write on the mailing list for these kind of things?? PS. ironically today they asked me for the first time in my life to check why Mailman was not working on a Linux server. The problem was that /var was full, but well knowing more about Mailman certainly helped :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
[Mailman-Developers] mailman UI
Look what I found reading the news, someone wants to make a social network out of Mailman ;) http://blog.linuxgrrl.com/2012/03/13/mailman-brainstorm/ ___ 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
