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). 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). 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. Best, Anthony
