On 11 April 2013 20:09, Chip Childers <chip.child...@sungard.com> wrote: > On Thu, Apr 11, 2013 at 12:51:34PM +0000, Abhinandan Prateek wrote: >> Yes, I think we need to space our releases further apart. > > That's a different discussion, which you are free to raise if you'd like. > >> Also community members should volunteer to own some part so that in above >> circumstances a person looking for some fix can approach that member, once >> again a suggestion. > > I've been reading through this thread, and I'll pick the "owner" comment > above as a starting point for my personal opinions. This is a reaction > to the whole thread really, so take a minute to read to the end please. > > "Owning some part" is antithetical to a healthy community approach. > Certainly people will gravitate to certain areas, and by all means > everyone should feel free to work on areas of the code-base that they > feel like they want to improve or support. This may lead to people > effectively being the primary "do-er" for certain areas (examples: Wido > has been working on DEB packaging, Rohit has been working on > CloudMonkey), but we shouldn't ever consider this ownership. I feel > personally welcome to make a change in CloudMonkey, and would certainly > consider it important to collaborate with anyone (especially Rohit) that > may have input and insights. > > The idea of ownership if a part of the software is something I'm strongly > against. > > Even the idea of maintainers seems like it is problematic in > implementation. How do we decide who the "official" maintainer is? How > do we decide when someone else should do that... And frankly, doesn't a > "maintainer" model really discourage others from working in named areas? > > All of these attempts to structure the community appear to be natural > responses when you have a background in corporate development (product > or otherwise), which is my background as well. It doesn't work here, > and you have to fight the urge to apply the same solutions (WRT > structure and process) in this environment. If you haven't read > "Producing OSS" [1], go do that. >
And if you don't have the patience, here's the appropriate extract: http://www.producingoss.com/en/managing-volunteers.html#delegation-assignment
