Ditto for my -1. I've always wanted to move Jenkins fork patches back to Jelly, but last time I worked on it Mavenizing the project and its components took too much time. Bruno
Sent from Yahoo Mail on Android On Thu, May 18, 2017 at 7:34, Oliver Heger<oliver.he...@oliver-heger.de> wrote: Hm, being a user of Jelly, I have the long-term goal to contribute to the project because I have indeed some itch to scratch, but unfortunately never got to it. So I am -1, but I cannot promise that I can work on Jelly in the near future. Oliver Am 17.05.2017 um 20:26 schrieb Benedikt Ritter: > Hi, > > I think we should move Apache Commons Jelly to dormant for the following > reasons: > > - Jelly hasn’t seen any activity in a while. There haven’t been any relevant > commits since 2010 (I didn’t search the history further than that…) > - The last release dates back to 2005. > - There is no activity in Jira or on our mailing lists. > > For this reason I’m calling a vote by lazy consensus for moving Apache > Commons Jelly to dormant. This vote will pass if nobody objects within the > next 72 hours, e.g. after 20-May 2017 14:30 EDT (UTC-4). > > Regards, > Benedikt > > > --------------------------------------------------------------------- > 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
