On Apr 4, 2011, at 12:37 PM, Chris Withers wrote: > Well, what has been happening, certainly from a (relatively) innocent > bystanders point of view is that it's all been on -devel up until now. > >> The two lists are meant to be a convenience for users, > > users, or developers?
Both. But obviously some of the developers spend 99% of their life on work, and 1% on developing pyramid. To then say they should also spend their time helping support with such a large community seems a bit crazy given that we aren't full-time open-source dev's on foundation funding or something. So yea, its a lot easier as a developer with limited time that wants to go over dev issues to skip the "how do I setup pip on OSX?" question, rather than spend that precious time wading through it. I'm not sure if thats elitism, or just basic time management. It feels like time management, and given the large community of users of this open-source project, I am thrilled to see many users step up to help other users get to where they are knowledge-wise. I personally read them both depending on time available on a given day. For users interested in the development issues, it seems easier as well. I mean, if being able to filter on a topic was not useful, surely there'd be no utility in having tags, categories, etc. in the world, eh? ;) > As a user and part time developer, I wasn't even aware of the -discuss list > until this discussion came up! Yea, bad communication. Again, very sorry we failed to foresee that one. >> We did take usage questions on -devel in the alpha days of Pyramid, to >> prevent Pyramid questions from confusing Pylons users. That's where >> all the confusion between the lists came from. That's over now. > > Really? ;-) Sure, we're trying to, thus this post. I suppose I could consider the nuclear option and wipe out the pylons-dev list entirely to force all discussion over to pylons-discuss, then at a later point bring back a development oriented list. But we're all adults, so that seems a bit childish and unnecessary. It would be nice if mail list threads could be 'tagged' or 'categorized' though. With a nicer UI and such a feature, that'd prolly be fairly similar to convore. Hell, it'd help me a ton just to see which libraries people needed help with, as I'm sure ppl that are expert in some libs could spend their time better answering just those questions. So being able to tag a thread 'Pylons 1.0' or 'Pyramid 1.0' or 'SQLAlchemy 0.6 + pyramid_sqla' would make it easy for people to know what the topic involves. Obviously mail lists weren't well designed for 'support' type things, which is why StackOverflow is so popular (which does have those tags!). Which presents another interesting discussion, should we refer people needing help to StackOverflow to see if their problem has a solution there, and if not have it solved there instead of on the mail list? Then we could just nuke pylons-dev, and have a single pylons-discuss where all Pylons Project related topics are discussed, and refer people with more 'support' type questions to StackOverflow. Just a thought. Cheers, Ben -- 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.
