On Wed, Jan 7, 2009 at 05:08, Ian Bicking <i...@colorstudy.com> wrote: > Mike Orr wrote: >> - Three Pylons CMS projects were started but last time i looked they >> were variously abandoned, undocumented, or didn't really seem like >> CMS's. > > Creating new projects that are going to be maintained long-term isn't a > good fit for GSoC.
I agree that this project is hard to scope for GSoC, but on the other hand it could include documentation updates (where out-of-date info is found). I think community would profit from such project. Especially if it would be well designed (eg. in community bonding period) - maybe keeping in mind possible plugins system implementation (or even writing it's basics during GSoC). The key here is to make features list, make priorities and based on this create scope for GSoC project. > Or creating a user management system based on repoze.who, > repoze.what, and a SQLAlchemy backend. Sounds like a nice project. I have never used repoze - I can't calculate whether scope for GSoC is appropriate. Regards, vArDo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
