[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Making your project more openŠhowto enable Gerrit

In my defense, the push to Git had two major motivators:

1) CVS is no longer supported and has--as I understand it--several major open bugs that aren't being addressed
2) With the introduction of Git, something had to go; Webmaster does not have infinite resources.

The push to Git had very real practical and pragmatic motivation.

Further, CVS was deprecated for a full two years before we started compelling projects to move. With that precedent established, you have until at least 2015 to accept Gerrit :-)

On a serious note, Eclipse projects are required to make reasonable effort to encourage and accept contributions. Adoption of Gerrit is one way of making this easy.

The Eclipse Foundation has no plan to force Gerrit on any project. PMCs may have a different opinion.

Wayne

On 10/04/2013 10:30 AM, Mickael Istria wrote:
On 10/04/2013 04:22 PM, Doug Schaefer wrote:
I almost wonder if we should just enable Gerrit for all projects. That's what we do internally here for all git repos that feed into product. It's great for all the reasons you mention Ed.
I can already imagine the various posts from Wayne on blogs/Twitter/mailing-list: "Move to Gerrit by the end of 2013, or get your project archived".
And then: "Disable direct push to Git repo and get every change on Gerrit by the end of Spring, or get your project archived".
And then: "Get Hudson CI posting feedback on Git reviews, or get your project archived".
Benevolent dictatorship at work ;)
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
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
          Europe 2013
Title: Re: [cross-project-issues-dev] Making your project more openÅ howto enable Gerrit
In my defense, the push to Git had two major motivators:

1) CVS is no longer supported and has--as I understand it--several major open bugs that aren't being addressed
2) With the introduction of Git, something had to go; Webmaster does not have infinite resources.

The push to Git had very real practical and pragmatic motivation.

Further, CVS was deprecated for a full two years before we started compelling projects to move. With that precedent established, you have until at least 2015 to accept Gerrit :-)

On a serious note, Eclipse projects are required to make reasonable effort to encourage and accept contributions. Gerrit is one tool that makes that easier.

Wayne

On 10/04/2013 10:30 AM, Mickael Istria wrote:
On 10/04/2013 04:22 PM, Doug Schaefer wrote:
I almost wonder if we should just enable Gerrit for all projects. That's what we do internally here for all git repos that feed into product. It's great for all the reasons you mention Ed.
I can already imagine the various posts from Wayne on blogs/Twitter/mailing-list: "Move to Gerrit by the end of 2013, or get your project archived".
And then: "Disable direct push to Git repo and get every change on Gerrit by the end of Spring, or get your project archived".
And then: "Get Hudson CI posting feedback on Git reviews, or get your project archived".
Benevolent dictatorship at work ;)
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
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
          Europe 2013