[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects

Hi,
 
Interestingly I just recently brushed the topic of broken or incompatible GitHub Issue connectors for Mylyn following the Mars Release Train with Task Top and Red Hat.
 
http://stackoverflow.com/questions/23613807/github-mylyn-connector-installation
mentions the problem exist for about a year now. 
This one http://stackoverflow.com/questions/4680400/mylyn-connectors-for-github-and-bitbucket?rq=1
claims, Eclipse Juno (4.2.2) came with GitHub Mylyn connectors already out of the box.
 
Mars doesn't. I just applied the Java ME 8 Embedded SDK to Mars.1 which as such works pretty neat, but was unable to connect to GitHub from Mylyn (an older installation of JBoss Tool Suite still works)
 
If people like myself work on multiple projects, in and outside Eclipse, it is inevitable that some of them use one system like Bugzilla, others use JIRA (let's not even go there about Mylyn support now;-) or GitHub. 
That's perfectly natural, and in an Open Source community ideally all or most of them should also be accessible via the preferred tools like Mylyn. Unfortunately at the moment it seems, some of these are no longer accessible to Open Source projects, but only work via paid commercial plug-ins like Task Top. Or having to use the Web outside your IDE. If that's the case, we'd be in a similar pickle as some said IntelliJ put most users with recent change in licensing models ;-O 
 
Regards,
Werner
 
Gesendet: Dienstag, 10. November 2015 um 10:53 Uhr
Von: "Ed Willink" <ed@xxxxxxxxxxxxx>
An: eclipse.org-project-leadership@xxxxxxxxxxx
Betreff: Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects
Hi

"I am pleased to announce that at last week's Board meeting,"

Maybe I am completely blind, but this comes a bolt out of the blue to me. Surely some discussion was merited?

If compatibility tooling is provided, I see a repeat of our longstanding ongoing NNTP/Forum synchronization disaster.

If tooling isn't provided we do a major disservice to all our committers and users, seemingly just to accommodate some projects who do not seem to be properly committed to Eclipse. Eclipse is a community that IMHO endeavors to provide a unified capability. We do not need fragmentation. (Unless of course we are all to move to GitHub.)

IIRC there was originally enthusiasm for using GitHub as a mirror for Eclipse GIT repos. Unfortunately this did not work. I suggest that efforts at GitHub support would be better spent on solving the GitHub mirroring rather than a flaky Bugzilla customization.

    Regards

        Ed Willink


 
On 10/11/2015 03:24, Mike Milinkovich wrote:
All,

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 eclipse.org 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.

Thanks,
--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223 (mobile)
 
 
 
 
_______________________________________________
eclipse.org-project-leadership mailing list
eclipse.org-project-leadership@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership

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.

_______________________________________________ eclipse.org-project-leadership mailing list eclipse.org-project-leadership@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership 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.