[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

Are there any plans to fix or improve the Mylyn GitHub issue connector, too?
 
It should pretty much use the same GitHub APIs and worked well until several months ago. Now at least in Mars installing it via Market Place fails with something like a "broken update link".
See earlier in this thread. The problem seems to exist for a while now. 
 
If some projects are able and allowed to use either issue tracker, then aside from occasional snapshots in either direction it would be great, if they could also track and update both from within the IDE in the same place, if they use Eclipse to work on their projects (which I assume, many do;-)
 
Task Top seems aware of the problem, but claim, GitHub was a "commercial vendor" and they or the Mylyn project don't feel obliged to support it out of the box. 
It feels a bit like lack of Maven/WTP support in M2E where after some time and discussions (and as I know first-hand also many big users shifting to alternatives like IntelliJ then) Red Hat took the lead and created M2E-WTP instead of Sonatype.
 
Werner
 
Gesendet: Mittwoch, 11. November 2015 um 08:54 Uhr
Von: "Wayne Beaton" <wayne@xxxxxxxxxxx>
An: eclipse.org-project-leadership@xxxxxxxxxxx
Betreff: Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects
Webmaster/Mike will correct me if I'm misstating.

At this point in time, there is no plan to mirror GitHub issues to Bugzilla or vice versa.

What we plan to do is regularly capture issues from GitHub in a manner that can be used to to import into another issue tracker should that need arise. i.e., we're going to pull the data out using GitHub APIs and cache it on our servers.

There is some discussion here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=442828

Wayne

 
On 11/11/15 01:25 AM, Greg Wilkins wrote:
 
On 11 November 2015 at 17:01, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
IMHO as soon as any significant project, Simultaneous Release today, could be any project tomorrow, does not contribute its issues to a Bugzilla search we have an unpleasant fragmentation and degraded reporting/diagnosis capability.
Ed, I agree that having complete information under eclipse infrastructure is important.   Jetty is one of the projects that would like to shift more towards github, but if bugzilla is to remain (as Mike indicated is will), then I think that github issues & comments should be mirrored to bugzilla and perhaps vice versa.
 
Having a single list of all issues, regardless of source, is valuable.   Currently we are manually creating bugzillas for PRs we receive from guthub, which is only really half a solution. If github ceased to exist, then we'd know an issue had existed, but would lose it's details and comments.   Thus automated mirroring and/or backup to eclipse sounds like a reasonable way to improve/safeguard something that is already happening now (partially) manually.
 
cheers

 
 


--
 
 
 
_______________________________________________
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.
 
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon
          Europe 2015
_______________________________________________ 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.

PNG image