[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gef-dev] GEF4 - Committer Nomination


Sorry for the late answer, but I see that the committer election does not go very well.

I am not sure whether I am entitled to vote (as a "Zest guy"), but if needed, I am ready to vote, as having new people aboard can help the GEF4 plans.

-- Zoltán Ujhelyi

Fault Tolerant Systems Research Group
Budapest University of Technology and Economics

On 2012.06.25., at 16:52, Anthony Hunter wrote:

> Sounds good to me, you can submit a committer election.
> Cheers...
> Anthony
> From:   Alexander Nyßen <alexander.nyssen@xxxxxxxxx>
> To:     GEF development <gef-dev@xxxxxxxxxxx>, 
> Cc:     Matthias Wienand <wienand@xxxxxxxxx>
> Date:   2012/06/21 05:41 PM
> Subject:        [gef-dev] GEF4 - Committer Nomination
> Sent by:        gef-dev-bounces@xxxxxxxxxxx
> My dear fellow committers,
> it has been about a year that we started the GEF4 provisional component 
> (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=347636 for details). 
> Our initial plan then was to create a new GEF4 Geometry API as a starting 
> point (an initial nucleus) and to port Draw2d/GEF 3.x code base to it 
> after the Juno release. While this is still valid, I am very happy that we 
> got our "Zest guys" into the boat as well, so the plan has been extended 
> to also migrate the Zest2 code base to it (after Juno as well) and to have 
> a unified modernization approach, labeled GEF4, afterwards (see 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=372365 for details). 
> Much work has thus been spent on creating the new GEF4 Geometry API in the 
> last year, and I am glad to announce that we will actually be able to 
> "release" sort of a first milestone of it shortly after the Juno release 
> (which I think can serve as a starting point for migrating the other 
> components as planned). This was only possible because Matthias Wienand, 
> who is an apprentice/student trainee that works at itemis under my 
> supervision, has contributed large parts to it (see 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=355997 for details; he has 
> also spend considerable work in building up the reference documentation 
> for GEF4 Geometry at http://wiki.eclipse.org/GEF/GEF4/Geometry and is 
> still doing so). I have talked with Matthias, and he is willing to further 
> support us with GEF4 (and I think he is capable to do so), so I would like 
> to nominate him as a committer on it (handling each contribution via a CQ 
> has become quite cumbersome). 
> As we have agreed here some time ago when initiating the GEF4 
> modernization approach, we wanted to start GEF4 as a provisional 
> component, seeing no need for an incubator project at first, and we wanted 
> to re-raise the question of whether to create an incubator or not in case 
> a) community wants to get actively involved or b) Juno has been released 
> (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=347636 for details). 
> Both is now pretty much the case. I am still of the opinion that we do not 
> need an incubator project to work on the GEF4 component, but this would 
> mean I had to nominate Matthias as a committer on GEF legal and we would 
> have to have some kind of gentleman agreement that he will only work on 
> GEF4 and not on the other components (similar to what we are currently 
> already doing w.r.t. to our other sub-component committership), in case 
> you guys elect him. What do you think?
> Cheers
> Alexander
> Dr. Alexander Nyßen
> Dipl.-Inform.
> Software-Engineer
> Telefon: +49 (0) 231 / 98 60-210
> Telefax: +49 (0) 231 / 98 60-211
> Mobil: +49 (0) 151 /  17396743
> http://www.itemis.de 
> alexander.nyssen@xxxxxxxxx 
> itemis AG
> Am Brambusch 15-24
> 44536 Lünen
> Rechtlicher Hinweis:
> Amtsgericht Dortmund, HRB 20621
> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
> Trompeter, Sebastian Neus
> Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael 
> Neuhaus
> _______________________________________________
> gef-dev mailing list
> gef-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gef-dev
> _______________________________________________
> gef-dev mailing list
> gef-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gef-dev