| Re: [eclipse.org-project-leadership] Use of GitHub Issues by Eclipse Projects |
Depending on interest and priorities, such an interface might be a good project for a future FEEP call. Just a thought.
The working groups, particularly Science, will benefit from tracking issues at GitHub.
As a point of reference, ORNL just finished migrating hundreds of internal repos to GitLab. We have more IT personnel than the Foundation has staff though. ;)
Jay
On 11/11/2015 2:54 AM, Wayne Beaton wrote: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.
That is my understanding as well. The EMO does not have the resources to build or maintain such a mirroring service. Our direction at the moment is to simply preserve freedom of action in the unlikely event that GitHub disappeared.
As always, if there was a community effort to build and maintain such an interface that could be of interest.
--
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.