> However, it seems that our common interest for a road-map, may not fit the > way you operate - as you said, if developers don't need a feature, it will > not be written. > This nulls the possibility of web2py developers answering the needs of > web2py users. >
Arnon, I think you are somewhat missing the point. This is not necessarily true of all open source projects, but at least with web2py, the users are the developers. Of course, not all users are developers, but contributions to the framework (as well as other aspects of community maintenance) come from users. As Massimo suggested, if some feature is really important or broadly useful, some user or users will end up working on it, likely because they themselves need it and are willing to put in the extra effort to generalize the solution. If nobody is willing to work on a particular feature, it is likely because there just isn't a strong enough need for it. If you're the only guy asking for something, don't expect someone else to do it for you. > I agree that a road-map should not contain deadlines - that makes sense (I > hate deadlines...:) ) - this way more efficient usage of man-power would be > possible, as the "eventual existence" of a well-written feature, is in most > cases of higher-priority to users than a > poorly-written-immediate-availability > of that same feature. This way, the person with the most > experience/knowledge of a given section of the code, would be the one to > develop that feature, however long it may take for him to get to it. > That was the point I tried to convey to Anthony - it feels like we see > more eye-to-eye on this point. > The point you conveyed was that you were unwilling to spend your time on a relatively easy task because you thought someone else could do it faster (though, it's starting to sound like you wouldn't be willing even if you could do it just as quickly, as you consider yourself to be a mere "user" who expects "developers" to respond to your needs). I have not suggested that we should prefer poorly-written features over well-written features merely to get the features sooner. I was actually making the opposite point -- that less expert users should work on the easy tasks (that they can do), even if it takes them a bit longer, leaving the more expert users to work on the harder tasks. And of course, there are always trade-offs -- we might prefer a competent but less sophisticated implementation next week over a comprehensive and complex implementation a year from now, particularly since the two options are not mutually exclusive. There is room for people of varying abilities to make contributions. If you don't want to be one of them, that's fine. Anthony -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
