On Thu, Jan 20, 2011 at 9:23 PM, chrism <[email protected]> wrote: > Hi all, > > I'm interested in planning one or more sprints for PyCon US in March. > As I'm mostly a "Pylons Project" guy, I plan to participate in tasks > that are related to that. > > It's hard to get a sense of the general state of the relationship > between TG and The Pylons Project at the moment. There is a "de jure" > relationship as described in > http://compoundthinking.com/blog/index.php/2010/12/28/turbogears-joins-the-pylons-project/ > but since that announcement there hasn't really been any traction > towards a "de facto" relationship. > > Is there any interest in creating sprint tasks that might help > solidify a defacto relationship between TG and The Pylons Project? I > have no solid suggestions personally, but maybe folks here have > various passions that could guide those sprints. >
Hi Chris, thank you for your call for action. Currently if I understood correctly the TG project is working on two separate paths: 1 - Projecting an evolution of TG based on Pyramid 2 - Maintain the current TG+Pylons project Currently I'm not really interested in the point 1 as it is a long term project, but I'm really interested in giving an hand to the point 2. As you stated we are now in a frezze status and currently the main problem that I see is related to project organization. I'll try to point out what is my perception. TG will become part of the Pylons project but: - Will the ticket/sprint management tools move on the pylons infrastructure? Where should we keep opening/closing tickets? Also the current TG trac is quite caoting a cleanup would be a huge improvement. - Who is currently in charge of the Doc sprint leadership? I really loved the work that M. Pedersen was doing before the merge announce, but lately he disappeared and it seems that we are now without a "tg doc boss". I saw some people recently proposing changes to the doc and asking where to send them without receiving an answer so bringing those people together will probably give a huge boost to the doc quality. - What should we do with the Development sprint? Chris Perkins was handling the TG2.1 and 2.2 releases and currently the TG2.2 release is really needed as 2.1 introduced a few bugs which should be fixed to maintain a good perception of the TG project to users. This is just my perception so it might be totally wrong, my main perception is that we are probably in a limbo and if we hang here too much we will just lose users appearing as a dead project. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
