Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Use of GitHub Issues by Eclipse Projects

I also think this is a great opportunity and look forward to it. I think any challenges with our present tool chain are also opportunities to make them even more awesome. I look forward to taking advantage of this as soon as the EMO is ready.

Thanks very much for working this issue for us!


On Nov 10, 2015 6:18 AM, "Jens Reimann" <jens.reimann@xxxxxxxxxxxxxxx> wrote:
This sounds like a great opportunity and I am really looking forward to this!

I also do guess there are a few obstacles in the way and some might even remain. So looking at a "great unified Eclipse Community" this may cause fragmentation.

But from the view of a project I do think if provides a great benefit, if the community of this project already is working on GitHub. I was a real fan of Bugzilla, but I also do think it just got stuck in the past. So telling contributers, which already work together on GitHub, to head over to Eclipse Bugzilla most likely scares them away. Which is in the end a bad situation for the project and therefore for the whole Eclipse Community.

And let's face it, with software we will always have fragmentation, and we have to learn an live with that. And it is a good thing! Everybody was crying for an alternative when IE6 was "the only browser" ;-)

Just my humble opinion on this one. Thanks for the effort!


On 11/10/2015 04:24 AM, Mike Milinkovich wrote:

Several years ago the Eclipse Foundation started allowing its projects to host their day-to-day development at GitHub. As part of that, we implemented several processes to ensure that Eclipse projects could maintain their freedom of action should GitHub ever go away, or dramatically alter their terms of service. A number of the projects which host their development at GitHub subsequently asked if they could also start using GitHub Issues, rather than Bugzilla for tracking issues.

I am pleased to announce that at last week's Board meeting, the Eclipse Foundation approved the following two resolutions:

Resolved, that with PMC approval, the Board approves the use of GitHub Issues for Eclipse projects which are hosted at GitHub. The EMO is instructed to backup GitHub Issues data on server infrastructure to ensure the future freedom of action of these projects.

Resolved, the EMO is instructed to provide instructions to Eclipse projects hosted on GitHub on how to properly utilize GitHub features (e.g. Release Pages) to remain compliant with the Eclipse project branding requirements, Eclipse Development Process, and the Eclipse IP Policy.
This does not mean that you can start using GitHub Issues for your project right away. It does mean that the EMO has started working on a plan to enable that, and we hope to do so soon. Please follow bug 481771 if you are interested in progress on this.

Mike Milinkovich
+1.613.220.3223 (mobile)

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

D-85235 Pfaffenhofen an der Glonn
Läutenring 43
Geschäftsführer / CEO: Dr. Thomas Heitzig

Amtsgericht München
Handelsregister Nummer  HRB 197959
USt ID: DE267945175

Office Munich
D 80992 München
Agnes-Pockels-Bogen 1
T +49 89 18 9 17 49 0

The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or pivileged
material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top