Has anyone created a Jira as a mechanism to track the decisioning process of classifying the other Jiras in a project? Just curious, because it seems more appropriate than having that discussion out here on the mailing list.
Thoughts? -Rob > On Apr 8, 2017, at 9:12 AM, Gilles <gil...@harfang.homelinux.org> wrote: > > Hi Rob, and all. > > [Your mail arrived a bit mangled with other posts.] > >> On Sat, 8 Apr 2017 08:05:07 -0400, Rob Tompkins wrote: >> > [...] >> >> >> You will have to pardon me Gilles, as I have, much like Gary, have been >> quite busy of late. I suppose the main question here should be: of the 101 >> open, in-progress, or reopened, jiras, which most need to be in 4.0. Can we >> sort them into two categories, 4.0 and 4.X? Do you mind if I try to make >> some headway in this area? I will continue to read through the issues to >> see wha >> > > [Seems there was something more you wanted to say.] > > Whatever you can do to clean up (request for feedback from the issue > reporter, sort issues, ...) is welcome of course. > > Let me be clearer (if I can): I do not (and cannot) request that > contributors spend more time than they have at their disposal. > But I would like to know whether the situation is here to stay, i.e. > whether committers have lost interest in helping with CM and related > stuff. > > I recall that I had announced, now almost a year ago, that > 1. I do not have the capacity to maintain CM all by myself, and that > it was/is (IMHO) a disservice to current and future users to let the > code rot, > 2. a viable alternative existed (IMO): more focused components (for > codes which active contributors could maintain). > > AFAIR, the proposal was well accepted by all "new" committers (5 people), > but not by the majority of PMC members (who spoke out). > > Since then, no PMC member has significantly contributed to CM so as to > advance towards a future release of the component as is (in the "master" > branch). > > I ask a simple and direct question to all PMC members: Is it now OK > to save the pieces of CM (so that each can be mended at its own pace, > waiting the necessary workforce to do so), or do you prefer that _all_ > the code gets less and less relevant (due to bugs or outdated practice > and that the community disappears? > > Thanks for your attention, > Gilles > > > > --------------------------------------------------------------------- > 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
