Web application frameworks and the future

Pierre-Yves Chibon pingou at pingoured.fr
Thu Jul 5 20:59:35 UTC 2012


On Thu, 2012-07-05 at 14:49 -0600, Kevin Fenzi wrote:
> On Thu, 28 Jun 2012 13:23:08 -0700
> Toshio Kuratomi <a.badger at gmail.com> wrote:
> 
> ...snip a bunch of stuff I agree with... ;) 
> 
> > My primary goal is to decide what framework to port our old TG1 code
> > to so that we can stop maintaining the TG1 stack before upstream
> > stops working on it at all.  My secondary concern is that we stop
> > growing the other stacks that we're maintaining and concentrate on
> > one or two which will make mainenance easier.  Can we choose two
> > frameworks right now that will suit our needs?  It seems that flask
> > can serve a niche and maybe should be one of them.  What should our
> > bells and whistles framework be?  TG2 or pyramid or something else
> > entirely?
> 
> I have no horse in this race, so I think if our application developers
> can chime in and reach a consensus thats good for me. 

I have to say that I have recently played quite a bit with Flask and in
the past I got some experience with TG2. Pyramid would be new to me, but
looking at the latest app from Luke, it does not look very far from TG2
and I think I would not be too lost.

> So, for TG1 apps thats: 
> 
> mirrormanager
> packagedb
> fas
> elections
> bodhi
> 
> One thing that might also weigh into this is existing porting work
> thats already been done to TG2. Ie, if developers would be willing to
> re-target pyramid or would prefer to go to TG2 due to existing work to
> move to that. 

One thing to consider as well is which of these apps have to be port to
the "bells and whistles framework"(© Toshio). From this list of TG1 app,
Ian is working on a Flask version of elections and there was a question
on the portability of MM to Flask as well (ie: light weight framework).

This leaves us with:
- packagedb
- fas
- bodhi
>From which bodhi should be removed in a not so long term with the
release of bodhi 2.0.
The last two (FAS and packagedb) have not had any attempt to port to
another framework (that I know off at least), so for these two the
choices of the framework is free.

In summary, my 2cts are: I know Flask and I quite liked working with it
for light weight application. I know TG2, but I am fine to try pyramid
if it's the preferred way to go.

Pierre


More information about the infrastructure mailing list