Hi all, Two things from me, a relatively new member of the community. I think much more effort needs to be on pushing things through code-review and to completion. There are many issues in LANG that have been awaiting review for well over a year or two. This means the commiters are no longer around to justify their decisions, and new contributors feel they are pushed aside whilst awaiting feedback.
Secondly, there are too many long discussions around various issues, leading to either flame wars on decisions or no action being taken at all. The project leads should take the comments made and make a decision on what is to be done after a sensible set of comments have been made. This would be hard with how few people run the project, but maybe this would help rebalance and focus the project. Would be willing to discuss this further Sent from my iPhone > On 29 Nov 2014, at 16:33, Thomas Neidhart <thomas.neidh...@gmail.com> wrote: > >> On 11/29/2014 11:53 AM, Benedikt Ritter wrote: >> Hi all, >> >> currently I feel really overwhelmed by the stuff I'd like to do at commons >> and the little time I can spend for it. Here is an (incomplete) list of the >> things I'd like to work on: > > Hi Benedikt, > >> - get a new release of the build plugin out of the door for auto creating >> README.md and CONTRIBUTING.md >> - Work on [VALIDATOR] and get a new release out of the door >> - Work on [DBUTILS] and get a new release out of the door >> - Push [lang] 3.4 out of the door >> - Have a look at [compress] 2.0 >> - Backport important fixes from [collections] 4.0 to 3.x and create a last >> service update >> - work on [text] >> - help releasing [imaging] 1.0 >> - Improve docs on how to get involved at commons >> - Organize a logo contest for commons >> - ... many more > > this sounds like you set your goals too high and are frustrated that you > don't get all the things done. I guess this is a common scheme for > ambitious/passionate people. Try to set more realistic goals and finish > them before doing other / more things. Then you will get the positive > feedback of achieving something and everything will be better. > >> I wonder how you feel about this. I have the feeling that a lot of people >> ask us to fix stuff and release components but we don't really catch up >> with this. This will give people the feeling that we are slow or we simply >> don't care. >> Whenever I see someone posting on JIRA "can you please fix this, we need >> this in out application" and nobody is reacting, I feel tempted to jump >> right in, even if I don't know the component (which adds another entry to >> the list above). >> I don't see a way how we can improve this. My feeling is, that we need more >> committers. But then I have the comments of people I've talked to in my >> ear: "to old school", "to difficult to get involved", "to slow development >> process", "to unwelcoming community". So what do we do? Do we need help? >> >> I'm excited to hear your thoughts :-) > > yeah, this is a general problem of commons imho. There are too many > components for a too small community as most of the original committers > have long left. > > The only way out is to do what we tried a couple of months ago: move not > maintained components to dormant, and keep the others alive with the > existing people. > > Just one example: jelly is a nice thing and actually used within jenkins > as the backbone html generator. But it is re-packaged within jenkins > custom bugfixes as the last jelly release (1.0) was in 2005. > > Similar things apply for el or primitives. > > These components are long dead and there are very good alternatives > available, so they should be abandoned. Cut off the dead branches to > keep the tree alive. > > Thomas > > --------------------------------------------------------------------- > 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
