Then maybe a bit of info around massimo being the BDFL (python/linux, benevolent dictator for life) being out there might work. As said before, seems very much like a perception problem rather than something that will be solved via some sort of company or group running things rather than a single person.
The current setup works great for me, but identifying that there are a few people (the list above is awesome) who are web2py experts, and very experienced in the code, even if there is a BDFL who is gatekeeper, and setting that as the expectation/perception going forward might well fix perception without any changes neccesary. Perhaps an "about the developers" page or something? Or an explanation of some sort on the web2py site? On Tue, Dec 28, 2010 at 2:42 PM, Jonathan Lundell <[email protected]>wrote: > On Dec 28, 2010, at 11:54 AM, VP wrote: > > > > I love the fact that if I have a problem with web2py and asked a > > question, Massimo will likely answer it. But the perceptual problem > > of web2py is a single-person effort is real. Massimo fixes most of > > the bugs (it seems so). Massimo is mainly responsible for PR. > > Massimo is in charge of experts4solution (it appears so). Massimo is > > mainly in charge of documentation (the book) (it appears so). > > > > Note that these are not necessary bad things. But the concern is > > real. Now, you can say this issue should not be a concern (i.e. we are > > okay with the current setup). Then that's a different perspective, a > > different story. > > Offhand, I can think of at least three major projects that have a single > person in charge, in one way or another: Linux, OpenBSD and Python. I don't > know much about the OpenBSD and Python patch processes, but all Linux > patches go through Linus. So in that sense, Massimo's role is not > unprecedented. > >
