All good points, Mariano. Thanks. Anthony
On Nov 19, 5:46 pm, Mariano Reingart <[email protected]> wrote: > On Fri, Nov 19, 2010 at 2:31 PM, Anthony <[email protected]> wrote: > > On Nov 19, 11:21 am, Mariano Reingart <[email protected]> wrote: > >> I don't fully understand this proposal, but, it shouldn't be posted on > >> web2py-developers? > >> BTW, is there a patch available? > > >> PS: I think we have to use web2py-developers more, just to not mix > >> issues that aren't relevant to users (and in fact, they may cause > >> confusion, wasted time, etc.)... > > > I think when talking about features/functionality, it makes sense to > > have some initial discussion on the users list, as users may want to > > weigh in regarding their needs/experience. When it comes to discussing > > the technical implementation of the features, though, then it may make > > sense to move the discussion to the developers list (though I suppose > > that can be hard to separate, as technical decisions may involve > > functionality tradeoffs). > > Yes, I think it is difficult to separate these threads, I think > sometimes they cause confusions, misconceptions, false expectations, > discussions that goes nowhere, users or developers that get upset, > mails that get lost in the wild, repetitive questions again and again, > FUDs or strange "recommendations" contrary to our objectives, etc. > > I don't think that this is good for web2py. > > > Also, I can't speak for all users, but I actually appreciate being > > privy to some of the "developer" discussions. It makes web2py seem > > more open and democratic (i.e., doesn't feel like there's some elite > > developers club making decisions to suit their own whims). > > Me too, I've found in web2py a open & friendly space not common in > other open source communities. > But please do not misunderstand me, developers are who finally > implement the changes, you can ask for something in the general list > but if no one have time nor interest in doing it, what is the point? > > I don't see a "elite developers club", as most patches are accepted by > Massimo, almost anyone can become a developer or can participate, > that's my case :P > > > One thought is rather than dividing the lists by roles (i.e., users > > vs. developers), maybe divide them by goals (i.e., usage/support vs. > > development). The "usage" list could be for questions, help, bug > > reports, community issues, announcements, etc., and the "development" > > list could be for discussing new features, roadmap, etc. Both users > > and developers could provide input on both lists (users who aren't > > interested in development issues could just stick to the "usage" > > list). Anyway, I think the web2py community is small and cohesive > > enough that we don't necessarily need this kind of separation right > > now, but maybe in the future. Just a thought. > > IMHO I don't agree on the last part, the general (user) list is having > too much traffic, so following it is becoming very difficult (at least > in my case). > > I think you're right about opening the developer list, so interested > "users" can provide input on both lists. > > I also think we must find other ways to participate, like web2py-wiki, > web2py-slices, polls (like logo contests), etc., so we can focus a bit > deeper and not to repeat ourselves. > > Best regards, > > Mariano Reingarthttp://www.sistemasagiles.com.arhttp://reingart.blogspot.com- > Hide quoted text - > > - Show quoted text -
