On 3/20/13 10:21 PM, Henri Yandell wrote: > Bike-shedding can be handled. > > Someone volunteers to RM a component. They put what they think needs > doing for the next release into a list (next JIRA version), and on > list we vote on which of the proposed components is top of the heap > for a swarm. Especially useful prior to an ApacheCon. Also useful to > use IRC as a place to hang out while swarming. > > With Lang in mind, the problem is not having an RM. It could have been > released any time in the last 12 months. So the above doesn't help > there; but many other components could do with swarming.
It does help in the [lang] case if the beginning is not "I want to RM [foo]" but "Does anyone want to RM [foo]?" or even just "how about some foo?" I agree this is an interesting idea and really just a small step beyond what we have been doing informally for years. As our "subcommunities" have dwindled for many components and the number of components has grown, getting more than just a lone committer to get involved in many things has gotten hard. So I agree it is a good idea to try to generate little "swarms" as you call them to increase collaboration. I think that was sort of Benedikt's point and it is a good one. Phil > > Hen > > On Mon, Mar 18, 2013 at 2:49 PM, Gary Gregory <garydgreg...@gmail.com> wrote: >> I appreciate your intention :) I feel this could lead to bike-shedding on >> the priority queue though :( It can be tough enough to agree to release a >> component as it is, without adding another level. >> >> What might work is something more informal like: "I've worked on [foo] and >> I've done all I need to get it to work for me. I'd like to see a release. >> What needs doing? Ah, this and that? OK, can you help?" Or, "I want to cut >> a [bar] release, can you please give a look before I waste cycles cutting >> an RC?" This is basically what I've been doing at least. >> >> There are too few of us IMO (except on [math] perhaps) to ask people to >> work on a given component which they may have no interest in, for work, or >> play. >> >> Gary >> >> >> On Mon, Mar 18, 2013 at 5:43 PM, Benedikt Ritter <brit...@apache.org> wrote: >> >>> Hi all, >>> >>> when looking through the components and the sandbox I can see that >>> development activity is very different. >>> We have very few components that are been worked on constantly, most >>> notably [math]. >>> >>> Some components seem to be worked on, only by a few people. [configuration] >>> comes to mind, where Oliver Heger is pushing a redsign of the API forward. >>> Thomas Neidhart is working on [logging] and in the same time prepares >>> [collections] for a 4.0 release. Oliver and Thomas are representatives for >>> other people that are not mentioned here, who put a lot of effort into >>> individual components. >>> >>> Furthermore we have some really promising APIs that have never been >>> released like [csv], [functor], [graph], [privilizer]. It's sad, that we >>> can not get those into a releasable state. >>> >>> Now I was asking myself how we can improve things. For me the collaboration >>> with other developers always is the most fun (and the most instructive). >>> This is why I was trying to get involved in more components recently. I >>> believe if several people work together on one component at a time, overall >>> development speed will increase. >>> >>> With this thread I want to bring up a discussion regarding medium-term >>> development goals for commons. It may be a good thing if could agree on >>> something like: "Until end of this year we want to push out collections >>> 4.0" or just "Let us focus attention on [csv] to finally push out the first >>> release soon". >>> >>> I know that most of us work for commons in their free time and almost >>> certainly want to develop on the components they are really interested in. >>> This is why my intention is not to create rules, like "nobody is allowed to >>> do commits for components other than [graph] until we have a release", but >>> to define a shared goal to focus resources and enhance development speed >>> and fun (at least for me ;-) >>> >>> WDYT? >>> Benedikt >>> >>> -- >>> http://people.apache.org/~britter/ >>> http://www.systemoutprintln.de/ >>> http://twitter.com/BenediktRitter >>> http://github.com/britter >>> >> >> >> -- >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 >> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
