I have had to turn down a handful of pull requests from github...I would be interested in knowing a way to disable that, or ideally accept github pull requests, that is unfortuanately a much cleaner mechanism then Gerrit.
I think I'll push in a Contributing file for jetty as well, probably not a bad idea...and align to a template once one exists jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Mon, Mar 25, 2013 at 4:36 PM, Aleksandar Kurtakov <akurt...@redhat.com>wrote: > ----- Original Message ----- > > From: "Wayne Beaton" <wa...@eclipse.org> > > To: cross-project-issues-dev@eclipse.org > > Sent: Monday, March 25, 2013 10:20:48 PM > > Subject: Re: [cross-project-issues-dev] 61 Contributions submitted on > GitHub > > > > > > The Architecture Council has been talking about providing a standard > > "CONTRIBUTING" template that projects can put into their Git > > repository root to describe how the project receives contributions. > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=397644 > > > > > http://wiki.eclipse.org/Architecture_Council/Contributor_Guide_Recommendation > > > > Any input, especially in the form of content for the template, is > > appreciated. > > Speaking of GitHub, is it possible for projects that handle contributions > only via Gerrit to opt out from the github mirroring or at least to have > the pull requests disabled so people don't try to submit this way. If noone > from the project cares about GitHub it simply sets false expectations to > potential contributors. > > > Alexander Kurtakov > Red Hat Eclipse team > > > > > Wayne > > > > > > On 03/25/2013 03:20 PM, Mickael Istria wrote: > > > > > > Hi all, > > > > I've noticed that some GitHub repo mirros have some pending > > contributions (issues or pull requests). I made a quick and dirty > > Groovy script to have a more global view of pending GitHub > > contributions (see attachement, replace GitHub username/password to > > run it locally). > > The following lists project who have contributions on GitHub: > > > > acceleo: 0 issues, 2 open pull requests > > bpmn2-modeler: 0 issues, 1 open pull requests > > ecf: 0 issues, 1 open pull requests > > eclipse.jdt.core: 0 issues, 1 open pull requests > > eclipse.jdt.ui: 1 issues, 1 open pull requests > > eclipse.platform.ua: 0 issues, 1 open pull requests > > eclipse.platform.ui: 0 issues, 2 open pull requests > > eclipselink.runtime: 0 issues, 4 open pull requests > > egit: 0 issues, 1 open pull requests > > egit-github: 0 issues, 5 open pull requests > > emf: 0 issues, 1 open pull requests > > gemini.blueprint: 0 issues, 1 open pull requests > > gemini.jpa: 0 issues, 3 open pull requests > > gyrex-releng: 0 issues, 1 open pull requests > > incubator: 0 issues, 2 open pull requests > > jetty.project: 0 issues, 1 open pull requests > > jgit: 0 issues, 3 open pull requests > > linuxtools: 0 issues, 4 open pull requests > > lyo.testsuite: 0 issues, 1 open pull requests > > m2e-core: 0 issues, 3 open pull requests > > nebula: 0 issues, 1 open pull requests > > orion.client: 0 issues, 6 open pull requests > > pdt: 0 issues, 4 open pull requests > > rap.incubator.fileupload: 0 issues, 1 open pull requests > > rap.incubator.gef: 0 issues, 1 open pull requests > > recommenders: 0 issues, 1 open pull requests > > rt.equinox.bundles: 0 issues, 1 open pull requests > > rt.equinox.p2: 0 issues, 1 open pull requests > > tycho: 0 issues, 2 open pull requests > > webtools.jsdt.core: 0 issues, 1 open pull requests > > webtools.jsdt.tests: 0 issues, 1 open pull requests > > webtools.sourceediting: 0 issues, 1 open pull requests > > ======================================== > > TOTAL: 1 issues, 60 open pull requests > > > > > > I think we need a way to get those contributions (and contributors) > > better integrated into the Eclipse ecosystem An appropriate solution > > would be a daemon looking for new contributions and adding a comment > > to the contribution to teach the author how to get it integrated > > into the project (via Bugzilla and Gerrit). > > > > Food for thoughts... > > > > -- > > Mickael Istria > > Eclipse developer at JBoss, by Red Hat > > My blog - My Tweets > > > > _______________________________________________ > > cross-project-issues-dev mailing list > > cross-project-issues-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > -- > > Wayne Beaton > > Director of Open Source Projects, The Eclipse Foundation > > Learn about Eclipse Projects > > EclipseCon > > 2013 > > _______________________________________________ > > cross-project-issues-dev mailing list > > cross-project-issues-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
