Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] IDE working group [WAS: Improving Eclipse JDT - Ecosystem]

On 2013-10-16, at 8:54 AM, Ian Bull <irbull@xxxxxxxxxxxxxxxxx> wrote:

> On Wed, Oct 16, 2013 at 8:33 AM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
> > If the member agrees to pay for a new platform developer then the path to committership should not be as hard as it is now for newcomers.
> 
>  
> 
> Yeah… That’s pretty much a non starter…
> 
> 
> +1. If a member company decides to fund a student for a 4 month work term to meet their commitment, I don't think we should ease the process and give that student platform commit rights because they are 'funded'. 

+1. As I've said before, w/ proper Gerrit implementation it shouldn't really matter.

For me, the #1 thing that a IDEWG (world's least sayable acronym! :D) needs to push to resolve is the problem of getting changes actually reviewed. Again, I don't think companies would actually pay for reviews -- they want features -- but perhaps with companies willing to pay for features, that could provide enough leverage to force proper reviews for platform and JDT. This may be controversial, but I think that reviewing outside contributions should be a minimal *requirement* of a core Eclipse project, just as participation in release train, bug triage etc.. is.

> 
> Cheers,
> Ian
>  
> 
>  
> 
>  
> 
> From: ide-dev-bounces@xxxxxxxxxxx [mailto:ide-dev-bounces@xxxxxxxxxxx] On Behalf Of Wim Jongman
> Sent: Wednesday, October 16, 2013 8:27 AM
> 
> 
> To: Discussions about the IDE
> Subject: Re: [ide-dev] IDE working group [WAS: Improving Eclipse JDT - Ecosystem]
> 
>  
> 
>  
> 
>  
> 
> I also think Gunnar pointed out some important key points: 
> 
> Every committer has to earn his wings by contributing to the project in a meaningful way. Even a developer financed by a member of the WG still has to get acceptance of the team he is contributing to. I don't see any difference of a committer coming from, say, Redhat contributing to P2, Platform or JDT and a developer payed by a member of the WG.
> 
>  
> 
> If the member agrees to pay for a new platform developer then the path to committership should not be as hard as it is now for newcomers. This is something that the WG could define as one of its main tasks.
> 
>  
> 
>  
> 
> Generally, we should not think of members of the potential IDEWG as sugar daddies. The WG is a mechanism build a platform for companies to give voice to their needs and pain points and finding people that have the resources to fix them.
> 
>  
> 
> I used the term "sugar daddy" in reply to Doug's comment about dictatorship. I just wanted to emphasize that committers, or those who pay them, have the final say in what get's implemented. Finding the members that are willing to commit development time to the commons should be another main task of the WG.
> 
>  
> 
> 
> _______________________________________________
> ide-dev mailing list
> ide-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ide-dev
> 
> 
> 
> 
> -- 
> R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
> http://eclipsesource.com | http://twitter.com/eclipsesource
> _______________________________________________
> ide-dev mailing list
> ide-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ide-dev



Back to the top