Bugzilla – Full Text Bug Listing
| Summary: | Request GitHub Issues access for N4JS project | ||
|---|---|---|---|
| Product: | Community | Reporter: | Jens Von Pilgrim <developer> |
| Component: | GitHub | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | derek.toolan, tokraemercli, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Jens Von Pilgrim
As per the Project Provisioning request, a GitHub Repo has been created here [1]. The empty repo does not have Issues activated as default. This can be requested, but must be approved by the Project Management Committee. More information can be found in the Project Handbook [2]. [1] https://github.com/eclipse/n4js/ [2] https://www.eclipse.org/projects/handbook/#resources-issues(In reply to Jens von Pilgrim from comment #0) > Would it be possible to move these issues to the new Eclipse Github project > later on? For what its worth, I not aware of a tool that would transfer Issues after the fact. Requested permission via technology-pmc mailing list (12.4., "[technology-pmc] Request GitHub Issues access for N4JS project"). We can transfer the existing repository to the Eclipse Foundation's organization if you'd prefer. That will require that we obfuscate the commit history of that repository, but would preserve the issues. Is that something that you want to consider? (In reply to Wayne Beaton from comment #3) That would be great! I already asked in the incubation mailing list about how you "obfuscate" the commit history, and I understand that you use a branch called "_old". What I do not understand is how this is obfuscated. When you transfer the existing repository, does that mean that the issues and pull-requests are transferred as well? (In reply to Jens von Pilgrim from comment #4) > What I do not understand is how this is obfuscated. Well unless you know to look in the '_old' branch it's 'hidden'. > When you transfer the existing repository, does that mean that the issues > and pull-requests are transferred as well? I think so, but I'm not 100% sure on that. -M. For the sake of simplicity we have decided to not convert any issues automatically. I'm not quite sure about the current status of this task: could we close it? It seems as if the issue are activated at https://github.com/eclipse/n4js/issues Can we simply start using that now? What about the bugzilla product "n4js". Is this to be deactivated? (In reply to Jens von Pilgrim from comment #6) > For the sake of simplicity we have decided to not convert any issues > automatically. > I'm not quite sure about the current status of this task: could we close it? > It seems as if the issue are activated at > > https://github.com/eclipse/n4js/issues > > Can we simply start using that now? > > What about the bugzilla product "n4js". Is this to be deactivated? When we get the go ahead from the IP Team to transfer the repo from [1] to [2], this will automatically pull in all existing Issues. As far as I am aware, there is not an option to disable this during the transfer. Please disregard the repo https://github.com/eclipse/n4js until we get the move started. Once the move is complete, all N4JS committers will receive notifications to join the N4JS GitHub Team, which will then grant write access to the repo. As Issues will be the canonical issue tracker, the Bugzilla instance can be removed - I will do that if there is no objection. [1] https://github.com/NumberFour/n4js/issues [2] https://github.com/eclipse/n4js (In reply to Derek Toolan from comment #7) > When we get the go ahead from the IP Team to transfer the repo from [1] to > [2], this will automatically pull in all existing Issues. We do NOT want the repo to be transferred! Instead, we want to simply to an "initial commit". (In reply to Jens von Pilgrim from comment #8) > We do NOT want the repo to be transferred! Instead, we want to simply to an > "initial commit". Thanks for the clarification. I have added the N4JS GitHub repo to the PMI [1]. This will in turn kick-off the webhook which will pull in all project committers for N4JS, and alert them to subscribe to the n4js GitHub team (so long as they have added their GitHub IDs to their Eclipse account [2]). This should happen within the next few hours, if it hasn't done so already. GitHub Issues has been activated on the repo. I have removed the Bugzilla component. [1] https://projects.eclipse.org/projects/technology.n4js [2] https://accounts.eclipse.org/ |