Yes, this was the primary reason why we were initially structured as subprojects under a parent project. As long as there are no common committers across all of the subprojects I think it would be hard to coordinate a common release. It would not be impossible (Eclipse does it but it takes a lot of process and overhead) but it wouldn't be fun, convenient to any of the subprojects, or useful to the consumers since nobody uses them all.
Thanks, -Mike Dear all, > It also has some disadvantages, i.e. all must release together I was not aware of this constraint – my understanding was that we treat them as one from an administrative point of view, not as code. Indeed, the projects are completely independent and releasing them together would not make any sense at all. Regards, Olaf Hi Mike, Rolling all sub-projects into one has some benefits, mostly less structure and thus less administration effort. It also has some disadvantages, i.e. all must release together. IMHO, having a project and sub-project structure makes sense if there is some common management across all projects. However, I think this is not the case. Each project is mostly independent. Is that the case? 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
_______________________________________________
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
|
