[Mailman GSoC] Archive UI Web Framework
Hi all,
I was looking for a web framework for Pipermail UI. I have decided to use Pylons. Anna and benste wanted to know the reasons for choosing pylons over Django (As benste is already using Django for mailman WebUI). So, I thought I should discuss it with all of you.
Andrew is working on converting Pipermail to use Storm/SQLite instead of pickles to save data. So, the framework needs to have support for Storm ORM. Django has its own ORM and Storm cannot be used with it natively (Though storm is said to have support <http://blogs.gnome.org/jamesh/2008/09/19/django-support-landed-in-storm/> for django, I could not find anything further to try/test Storm with Django). Pylons doesn't provide any ORM and I have tested a small application using Storm.
Please give your feedback.
Regards, Dushyant
Hi,
you might want to take a look at arbrows, developed by Nahuel, that does about the same as what you're planning to do!
http://www.arbrows.org/browser/src/arbrows
see it in action at http://archives.rezo.net/
On Wed, Jun 22, 2011 at 8:10 PM, Dushyant Bansal <cs5070214@cse.iitd.ac.in> wrote:
Hi all,
I was looking for a web framework for Pipermail UI. I have decided to use Pylons. Anna and benste wanted to know the reasons for choosing pylons over Django (As benste is already using Django for mailman WebUI). So, I thought I should discuss it with all of you.
Andrew is working on converting Pipermail to use Storm/SQLite instead of pickles to save data. So, the framework needs to have support for Storm ORM. Django has its own ORM and Storm cannot be used with it natively (Though storm is said to have support <http://blogs.gnome.org/jamesh/2008/09/19/django-support-landed-in-storm/> for django, I could not find anything further to try/test Storm with Django). Pylons doesn't provide any ORM and I have tested a small application using Storm.
Please give your feedback.
Regards, Dushyant
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/fil%40rezo.net
Security Policy: http://wiki.list.org/x/QIA9
-- Fil
Hi,
There is some modifications that have not yet been pushed to the repository. I will when I get time.
If you are interested I can integrate your patches, and explain how it works. I'm on freenode IRC server.
Bests,
Le 24/06/2011 09:31, Fil a écrit :
Hi,
you might want to take a look at arbrows, developed by Nahuel, that does about the same as what you're planning to do!
http://www.arbrows.org/browser/src/arbrows
see it in action at http://archives.rezo.net/
On Wed, Jun 22, 2011 at 8:10 PM, Dushyant Bansal <cs5070214@cse.iitd.ac.in> wrote:
Hi all,
I was looking for a web framework for Pipermail UI. I have decided to use Pylons. Anna and benste wanted to know the reasons for choosing pylons over Django (As benste is already using Django for mailman WebUI). So, I thought I should discuss it with all of you.
Andrew is working on converting Pipermail to use Storm/SQLite instead of pickles to save data. So, the framework needs to have support for Storm ORM. Django has its own ORM and Storm cannot be used with it natively (Though storm is said to have support <http://blogs.gnome.org/jamesh/2008/09/19/django-support-landed-in-storm/> for django, I could not find anything further to try/test Storm with Django). Pylons doesn't provide any ORM and I have tested a small application using Storm.
Please give your feedback.
Regards, Dushyant
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/fil%40rezo.net
Security Policy: http://wiki.list.org/x/QIA9
-- Nahuel ANGELINETTI
On Jun 24, 2011, at 09:49 AM, Nahuel ANGELINETTI wrote:
There is some modifications that have not yet been pushed to the repository. I will when I get time.
If you are interested I can integrate your patches, and explain how it works. I'm on freenode IRC server.
Perhaps you can post that here! I'd certainly be interested in hearing about it.
Note too that Mailman 3's architecture allows for integration with multiple archivers, so it would be cool to get a shim for arbrows. Have you looked at the interface for that? Perhaps you could contribute some code for it.
-Barry
On Jun 22, 2011, at 11:40 PM, Dushyant Bansal wrote:
I was looking for a web framework for Pipermail UI. I have decided to use Pylons. Anna and benste wanted to know the reasons for choosing pylons over Django (As benste is already using Django for mailman WebUI). So, I thought I should discuss it with all of you.
Andrew is working on converting Pipermail to use Storm/SQLite instead of pickles to save data. So, the framework needs to have support for Storm ORM. Django has its own ORM and Storm cannot be used with it natively (Though storm is said to have support <http://blogs.gnome.org/jamesh/2008/09/19/django-support-landed-in-storm/> for django, I could not find anything further to try/test Storm with Django). Pylons doesn't provide any ORM and I have tested a small application using Storm.
I don't have much personal experience with Pylons, but I've heard good things about it.
As long as Pipermail is still in the core, I do think it makes sense to continue the work to port it to Storm, since that's the ORM that the core uses. We've talked about splitting Pipermail off into a separate sibling project (much like the new UI is currently), and if we do that, I'd be open to re-evaluating the choice of Storm for Pipermail.
I don't want to throw a monkey wrench into Andrew's work of course, just saying that if there was compelling reasons to want Django and its ORM for Pipermail, the way to do it would be to split off Pipermail first.
OTOH, I'm perfectly fine with the current direction you and Andrew are taking with the GSoC projects.
Cheers, -Barry
On Jun 24, 2011, at 7:51 AM, Barry Warsaw wrote:
As long as Pipermail is still in the core, I do think it makes sense to continue the work to port it to Storm, since that's the ORM that the core uses. We've talked about splitting Pipermail off into a separate sibling project (much like the new UI is currently), and if we do that, I'd be open to re-evaluating the choice of Storm for Pipermail.
I don't want to throw a monkey wrench into Andrew's work of course, just saying that if there was compelling reasons to want Django and its ORM for Pipermail, the way to do it would be to split off Pipermail first.
Cheers, -Barry
I agree that the preferred design approach is to split the project into a number of independent modules that communicate through traffic queues / channels and a database which stores the settings.
I don't know that much about the various ORM schemes. Could someone explain why the STORM is preferred to the Django ORM or that used in Pylons?
On Jun 24, 2011, at 08:16 AM, Richard Wackerbarth wrote:
I don't know that much about the various ORM schemes. Could someone explain why the STORM is preferred to the Django ORM or that used in Pylons?
I like Storm because it's a lightweight layer on top of dbapi and SQL. There's not much guessing about what's really happening under the hood, and the library itself is pretty small so it's easier to reason about what a particular expression is going to translate to.
It's also heavily battle tested, e.g. in Launchpad, which is way, way bigger than Mailman will ever be. Of course it's also free software and GPL compatible, which is critical to Mailman's use.
The biggest complaint I have is that it's a bit under documented. OTOH, I've also found it's pretty easy to use given the existing documentation, and because the code is small, well-tested, and nicely organized, it's easy to dip into it for the few times I've needed to.
Cheers, -Barry
participants (5)
-
Barry Warsaw -
Dushyant Bansal -
Fil -
Nahuel ANGELINETTI -
Richard Wackerbarth