Re: [tools-pmc] [Request] Buildship - Appeal of PMC decision

[Doug Schaefer <dschaefer@xxxxxxx>]

As a clarification, it was the Tools PMC, myself in particular with the
help of Wayne, that brought the exception request to the Planning Council.
It was the Planning Council that rejected the request.

Doug.

On 2015-04-17, 11:45 AM, "Etienne Studer" <etienne.studer@xxxxxxxxxxxxxx>
wrote:

>Dear EMO and Tools EMC
>
>We would like to ask for your support and assistance in appealing the
>decision taken by the PMC that Buildship is not accepted into the Eclipse
>Mars simultaneous release.
>
>There are several reasons why we think an appeal is justified:
>
>The decision process did not involve the actual project leads of
>Buildship. We could have given clarifying input on several of the
>discussed items and most likely could have resolved some of the expressed
>concerns.
>
>One of the concerns expressed was that Buildship would not meet the
>quality expected by the Eclipse community. We believe that these concerns
>are not justified since Gradleware consists of highly qualified,
>experienced software developers that know how to deliver reliable
>software to large audiences. On top of that, we have received excellent
>mentorship from Wayne Beaton to ensure we match the requirements for
>inclusion in the simultaneous release. We have also already received and
>incorporated feedback on Buildship from Eclipse experts like Stefan
>Oehme, Eike Stepper, and Lars Vogel. Additionally we have been developing
>and using the core of the Buildship for internal projects since the
>middle of last year.
>
>There are many developers and companies asking (screaming) for
>first-class Gradle support in Eclipse, as we know from the Gradle
>community. We have already asked for and still gather feedback from some
>of these individuals and entities to ensure the already provided features
>are functional and useful. Additionally, as of next week, vogella gmbh,
>the company of Lars Vogel, will bring in their Eclipse expertise and
>contribute to the development of Buildship throughout the rest of the
>year on a regular base. This will further ensure Buildship is developed
>and integrated the Eclipse-way.
>
>Gradleware has invested a lot into Buildship. Also based on the
>perspective of being included in the Mars release, we as an organization
>had made some painful prioritization decisions not to do other important
>work so that we can be ready with Buildship for Eclipse Mars. The
>Buildship team has been working full-time and with total focus on
>Buildship, and will continue to do so. We do not take the commitments
>that come with the inclusion into Eclipse Mars lightly. We are fully
>committed. We have proven over the past few months that we react very
>quickly to match any inclusion requirements.
>
>Gradle has a high amount of traction in the enterprise. LinkedIn,
>Netflix, Twitter, Google, Nike, Gap, and many others rely strategically
>on Gradle. Offering them first-class Gradle support in Eclipse is a must
>in order for Eclipse to remain relevant. Waiting with the inclusion of
>Buildship into the simultaneous release until June 2016 will continue to
>make users and companies switch to IntelliJ IDEA which already has a very
>decent Gradle integration today, and which will have an even deeper
>integration with Gradle in the upcoming releases.
>
>
>Kind Regards, the Buildship Project Leads
>
>Hans Dockter, CEO of Gradleware and Founder of Gradle
>Etienne Studer, VP of Product Tooling Gradleware
>
>_______________________________________________
>tools-pmc mailing list
>tools-pmc@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/tools-pmc