Re: [eclipse.org-architecture-council] [eclipse.org-project-leadership]

[Denis Roy <denis.roy@xxxxxxxxxxx>]

On 12/11/15 12:15 PM, Julien Ponge wrote:
> Of course it is very important for the Foundation to have a referential of issues and discussions, so mirroring to Bugzilla or anything else (DB?) is a must.

Just to clarify the terminology -- we won't be mirroring GH Issues to 
Bugzilla, just like we don't keep public mirrors of GH repos. Think of 
our copy of GH data as a backup, outside of the public view.

That is probably what you meant, but I felt the need to clarify.

Denis



> Another thing to consider: pull-requests are just a very special type of issue, so when you need to craft a release GitHub gives you a whole set of issues, pull-requests, and the associated discussions.
>
> It’s our practice to always discuss around pull-requests, never much in Bugzilla issues. Pull requests are more than mere code reviews, they are part of the workflow. If you look at our first release issues [2] it gets crystal clear: we did not even bother creating Bugzilla entries for most of the features and fixes. It’s not that we don’t want to adhere to the Eclipse Development Process. No, it’s really a matter of keeping the workflows simple, and our pre-Eclipse habits where GitHub-biased, so a double bookkeeping between PRs and issues has little perceived value.
>
> Hope it helps :-)
>
> Cheers
>
> [1] https://projects.eclipse.org/projects/technology.golo
> [2] https://projects.eclipse.org/projects/technology.golo/releases/3.0.0-incubation/bugs
>
> - Julien
>
> > On 10 Nov 2015, at 04:24, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx> 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,