Hello everyone, I'm one of the developers of Kallithea, a source code hosting and review system, which is currently based on Pylons 1.0. As we're busy polishing essential features of the software, we don't currently have time or manpower to migrate to some less obsolete framework, so we stick to Pylons. It happens we need certain things to be fixed in Pylons, but it seems the old code doesn't receive much love these days and it's not really well-maintained.
I wonder, what if we take over the maintenance of the project and so that we can keep it more alive than it is currently? We'd really not like to have our own fork of Pylons :) [0] https://kallithea-scm.org/ -- Cheers, Andrew -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
