It is very sad to see a project failing at growing a community. Looking at the various public sources, I see:
- just 2 pull request since its start in incubation - no postings on the user ml since December 2015 - only 3 committing contributors since start in incubation - No description (readme) in github - No mission statement/goal description of the project on the project's home page I fear this will not turn around due to the lack of interest in the world beyond the project. At the moment I am inclined to say: time for retirement. Best regards, Pierre Smits ORRTIZ.COM <http://www.orrtiz.com> OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Sat, Apr 15, 2017 at 5:07 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi John > > I think you did the right thing by bringing the point on the table. > > AFAIR I already stated some months ago that, regarding the activity and > regarding the community around, we should really think about retirement of > Sirona. Some can argue about the fact that Sirona is a "stable" project > that's not really valid: if it's valid we should see questions, feature > requests, etc coming from the user community. And obviously it's not the > case. So I think that Sirona is just use for specific use cases in a very > limited community. > > My €0.01 ;) > > Regards > JB > > On Apr 15, 2017, 15:49, at 15:49, "John D. Ament" <johndam...@apache.org> > wrote: > >All, > > > >I hate bringing up these topics. But I think we as the IPMC we have to > >take a close look at how Sirona is running and figure out what to do > >next. > > > >- The podling has not reported in several months (this is their 3rd > >attempt > >at monthly). > >- Every time the thought of retirement comes up, a little bit of > >activity > >on the project happens. It doesn't sustain. > >- There is some limited project history, but no real contribution in 6 > >months ( https://github.com/apache/sirona/commits/trunk ) > > > >I personally don't want to see projects go, and I don't want to force a > >project to leave, but at the same time I'm not convinced that there's > >enough of a community behind the project to sustain it going forward. > >They've put together a limited plan to get a release out the door, but > >other than that I'm not sure they're going to be able to move forward. > > > >So I want to ask, as the IPMC, do we want to give them time to regroup? > > > >John >
