We need a little more from the Tools PMC.
Naturally, Buildship will need to release. I assume that getting PMC
approval for a release should be relatively straightforward. In
order to join any packages, it will need to graduate (package
maintainers likely will not accept an incubating component). What
needs to happen in order for the PMC to approve a release/graduation
review in time for Mars?
What, in the opinion of the PMC, must happen for Buildship to join
Mars?
How do we (you) bring this to the Planning Council?
Some points to ponder:
* Just because we haven't done this before, isn't good enough reason
to not do it now.
* Buildship is doing a very good job of building community [1]
* Buildship has had more support through the onboarding process than
pretty much any other project that I can recall
* AFAICT, they've got everything in the right place as far as the
EDP, IP Policy, and Mars participation requirements are concerned.
* We at the EF feel that this is a really important bit of
technology for Java users.
* They are a "leaf" node in the dependency graph, so the overall
risk is low.
* Reward vs. Risk is high IMHO
What else?
How about we set up a call for 10 am EDT tomorrow?
Tools PMC call-in info:
- North America +1-866-569-4992
- Germany +49-692-2224-6059
- France +33-(0)-17-070-8535
- UK 0800-033-7806
- Switzerland +41-44-580-2115
- Sweden +46-85-063-8386
- Italy 003-902-3604-8268
Participant conference extension: 717 then enter pin: 57932
Wayne
[1]
http://blog.vogella.com/2015/04/17/buildship-on-the-mission-to-mars/
On 20/04/15 11:09 PM, Doug Schaefer
wrote:
Sorry, I was waiting for David to comment. I don’t really
have anything to add. I believe the PC was aware of all of this
information when the PC decision was made. And I gave it a good
fight. I’m not sure there’s any more the PMC can do. But I’d
attend a call if we thought it would be fruitful.
Doug.
Hello Tools PMC,
In case it's not clear, Etienne is seeking your direct
help in appealing the decision made by the Planning
Council.
If it would be helpful, I can schedule a conference call
to bring the parties together and discuss the issue. My
calendar has some availability on Wednesday.
Please let me know I how I can help.
Wayne
On 17/04/15 12:00 PM, Etienne
Studer wrote:
Dear EMO and Tools PMC
We would like to ask for your support and assistance in appealing the decision taken by the PC 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
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
![EclipseCon France 2015]()
---------------------------------------------------------------------
This transmission (including any attachments) may contain
confidential information, privileged material (including material
protected by the solicitor-client or other applicable privileges),
or constitute non-public information. Any use of this information
by anyone other than the intended recipient is prohibited. If you
have received this transmission in error, please immediately reply
to the sender and delete this information from your system. Use,
dissemination, distribution, or reproduction of this transmission
by unintended recipients is not authorized and may be unlawful.
_______________________________________________
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
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
|
