I like the idea behind http://trypyramid.com, which looks nice and has a Pylons Project logo at the bottom and clearly says "Pyramid is a project of the Pylons Project". I get a clear idea of the difference between Pyramid and Pylons.
The confusion between all the different 'brands' that seem to come up when Pyramid is mentioned was actually one of the reasons it took me this long to try Pyramid. Pyramid comes up once in a while on Reddit and people have really good things to say, and everytime I would read the comments or follow links I'd get confused between words like Pyramid, Plone, Pylons, Zope, Repoze that would pop up. Embarrassing as it is to admit, that's why I never gave myself a chance to try the framework that's now my favorite. Compare it to Flask's website where in a few seconds you know exactly what it is and what next steps to take. And it looks modern and gives the feeling that it's active and recent (first impressions and all), then there's a separate, clean documentation index page http://flask.pocoo.org/docs/0.10/. Is trypramid.com source on Github? I personally would contribute in making it really clear and accessible for newcomers, since I'm one myself. On Saturday, December 27, 2014 2:58:29 AM UTC+1, Randall Leeds wrote: > > I'll echo this sentiment. If we want to discuss it further, we should > start a separate thread for it, because I don't want to derail the > conversation about project organization and branding. > > I'm the sort, though, that would follow this conversation and chime in > here on the mailing list but would probably not participate if it moved to > Slack, unless I can do so via IRC without signing up. > > On Fri, Dec 26, 2014, 10:44 Michael Merickel <[email protected] > <javascript:>> wrote: > >> Sorry I'll say more than "it bothers me". It's an invite-only system >> that seems counter to the principals of contributing to an open source >> project. Even with its irc support enabled. >> >> On Fri, Dec 26, 2014 at 12:40 PM, Michael Merickel <[email protected] >> <javascript:>> wrote: >> > I'll go ahead and be that guy who says he doesn't like seeing his open >> > source community move away from irc. Sure slack may work with irc but >> > is there actually a problem with just using irc?? This is maybe the >> > 2nd or 3rd pyramid discussion I'm seeing offloaded to slack and it >> > bothers me. >> > >> > Back to the original discussion, why the sudden push for subdomains? >> > We could easily just re-org things under pylonsproject.org and make it >> > significantly easier to secure with https in the future. >> > >> > On Fri, Dec 26, 2014 at 11:40 AM, Bert JW Regeer <[email protected] >> <javascript:>> wrote: >> >> Speaking of Slack, what’s the info and how could I join? >> >> >> >> Bert >> >> >> >>> On Dec 26, 2014, at 15:55, Paul Everitt <[email protected] >> <javascript:>> wrote: >> >>> >> >>>> >> >>>> On Dec 26, 2014, at 9:50 AM, Blaise Laflamme <[email protected] >> <javascript:>> wrote: >> >>>> >> >>>> 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 :) >> >>> >> >>> Sounds fun. Let’s create a #pylons there..oh wait, we don’t want to >> perpetuate the word “Pylons”…oh wait, we want to reinforce it as an >> umbrella. Core dump. :) >> >>> >> >>> I think a Slack channel would be good. >> >>> >> >>> —Paul >> >>> >> >>>> >> >>>> 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] <javascript:>. >> >>>> To post to this group, send email to [email protected] >> <javascript:>. >> >>>> Visit this group at http://groups.google.com/group/pylons-discuss. >> >>>> For more options, visit https://groups.google.com/d/optout. >> >>> >> >>> >> >>> -- >> >>> 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] <javascript:>. >> >>> To post to this group, send email to [email protected] >> <javascript:>. >> >>> Visit this group at http://groups.google.com/group/pylons-discuss. >> >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> >> 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] <javascript:>. >> >> To post to this group, send email to [email protected] >> <javascript:>. >> >> Visit this group at http://groups.google.com/group/pylons-discuss. >> >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/pylons-discuss. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
