|Re: [ide-dev] Improving Eclipse JDT - Ecosystem|
On 10/14/2013 05:45 PM, Marcel Bruch wrote:
Getting this part of the EPP packages doesn't require much human resources.So, there is definitely a lack of human resources.
My employer is totally fine with having people contributing to Eclipse projects, it's even more or less part of our job. So in that case, it's not an employer or company issue. I guess all people reading that are encouraged by their employer to contribute, so I don't think we can blame those companies for not providing enough.I don't know. Do you know (for your company)?
From my experience with contributing to JDT or Platform in general, the bottleneck is currently the ability to get contributions reviewed. There are currently only a few people who are able/skilled to make review for JDT patches, so getting reviews takes lot of time, especially if your contributions is not part of the Platform team Roadmap.
The fact that there is a roadmap for Platform makes it more difficult to get external contributions considered/reviewed/approved. Ideally, this would be solved by having much more diversity in the Platform contributors, and not having them all following a roadmap. However, I have to admit that it is difficult to become a "good enough" contributor in Platform/JDT to be made a committer, so it's difficult to provide this diversity. And the upcoming support for Java 8 doesn't help. So we are in a deadlock for now.
What we can hope is that once Java 8 is done, their will be more space for community contributions inside Platform & JDT.
Back to the top