You're right about this issue and I think time has come to do something. Me and Paul started some efforts on this and never finished it but we were on a good track I think. What I suggested him lately was to streamline and narrow the original scope and start work on unifying what we have.
For sure I need to finish the brand stuff I already started and spread it across what we already have online but we also need to rethink how the information is structured and how we relate everything. I propose to move this discussion over slack :) On Friday, December 26, 2014 1:56:07 AM UTC-5, Sontek wrote: > > There is a lot of confusion around the "Pylons" organization and I think > in general our http://www.pylonsproject.org/ website doesn't help > alleviate any of that confusion. For example you can't even go to > http://www.pylonsproject.org/projects and get a list of Pylons projects, > this just redirects to Pyramid's about page. > > I feel we should decide which are "official" pylons projects and make it > extremely obvious which ones fall under this umbrella. Off the top of my > head the following are ones probably worth listing under this umbrella: > > https://github.com/Pylons/colander > https://github.com/Pylons/deform > https://github.com/Pylons/substanced > https://github.com/Pylons/venusian > https://github.com/Pylons/waitress > https://github.com/Pylons/webtest > https://github.com/Pylons/webob > > Now they all already live under the /Pylons/ organization on github but > there are plenty of less "complete" projects underneath that organization > that makes it hard to track down which are ready for prime time. > > The other big issue is a lot of these live under their domain, under > pythonpaste.org, or don't have a website outside of readthedocs at all. > > I propose that we create subdomains for each of them and make sure to be > consistent on including a footer that mentions that they are pylons > projects. This would be similar to how the Apache organization manages > their projects: > > http://kafka.apache.org/ > https://spark.apache.org/ > http://cassandra.apache.org/ > > and how pocoo does it: > > http://flask.pocoo.org/ > http://click.pocoo.org/ > http://werkzeug.pocoo.org/ > > It would probably also make sense to try to maintain a more consistent > brand across each projects website as well. Allowing each project to have > some personality of their own will be important by keeping a standard color > scheme and layout would help people recognize a pylons project immediately. > > What do you wonderful humans think? > > - sontek > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
