Hi,
I am responsible for “Gemini DBAccess”. However, like Mike, my focus at work has changed, and I do not have the time to support the project as needed. Mike and me have been exchanging thoughts
on the subject – but so far, we haven’t been able to come up with a good solution. It might be possible to merge related Gemini subprojects, for example Gemini JPA and Gemini DBAccess to reduce the administrative overhead. But it would still be necessary to
find someone who is able to devote some of his/her time to the project. The current setup has the advantage that it transparently shows, which parts of Gemini are actively developed, and which are not. With one big Gemini project one might lose some of that
transparency.
Best regards,
Juergen
From:
<rt-pmc-bounces@xxxxxxxxxxx> on behalf of "michael com>" <michael.keith@xxxxxxxxxx>
Reply-To: "'rt-pmc@eclipse. org'" <rt-pmc@xxxxxxxxxxx>
Date: Wednesday 10 August 2016 at 21:55
To: "'rt-pmc@eclipse. org'" <rt-pmc@xxxxxxxxxxx>
Subject: Re: [rt-pmc] Gemini-blueprint: Need help reviving the project
As the leader of the Gemini project I guess I should chime in…
Gemini already is a single project, with 6 subprojects. Given that each of the subprojects is quite different from the others the hypothesis was that nobody would want to consume all of them, and in fact, this has proven itself to be true
in that never has anyone contributed or expressed an interest in all 6. This makes me think that nobody would want to lead all 6, much less maintain them.
However, Gemini has been wallowing for a few years, since I became engaged in a completely different product line, and if somebody wants to take it on I would be more than happy to pass the baton. I asked internally to see if there was
any interest in taking on Gemini JPA, the subproject that I also lead, but did not get any nibbles at that time. Since then I have been keeping up with the very infrequent forum posts, but the project has been on life support for awhile.
sure, if there is a pool of committers to bring in, sounds like this component is suffering in general
+1 for rolling it all into one project if it isn't, that would at least bring the component into other active committers domain
looks like rollup might be tough as well, it looks like it is suffering from lack of activity overall
On Tue, Aug 9, 2016 at 2:44 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
I'm not sure this is a technology issue (GitHub vs. Gerrit). It sounds more like a resource/staffing issue.
FWIW, it's pretty easy to reboot a project at Eclipse. We just need proof that it's dysfunctional and we as PMC can replace/bring in new committers. I don't think GitHub can do this to any project hosted there.
-Gunnar
Would it be better to attic the project here and let someone fork it to github where it is more likely to pick up more general interest? I don't know that the overheard of an Eclipse project is desirable when trying to build a community
up from scratch.
Or is gemini itself doing fine and it is just a singular component having issues, if that is the case then rolling it into another component would likely be a better option?
On Tue, Aug 9, 2016 at 1:57 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
Hi All,
I just returned from vacation. Has the discussion been progressed? If the gemini-blueprint project is unresponsive we should talk to Olaf if he is interested in bringing it forward and being added as a committer.
-Gunnar
I am a contributor to the gemini-blueprint project. Since the 2.0.0 release in March, I am in need of further assistance by the project lead’s to consolidate some general project
issues. However, the lead seems to lack resources as I was unable to get feedback since then.
I would appreciate if the PMC could clarify whether re-election of project leadership for gemini-blueprint is required to get things moving again.
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|