Re: [gef-dev] GEF3 resurrection

[Alexander Nyßen <nyssen@xxxxxxxxxx>]

Hallo Serge,

thanks for bringing this up. In fact, developers who „eagerly want to contribute and/or maintain“ GEF legacy have not stepped up in the past. 

We therefore ensured that the GEF-legacy code base was migrated to Github before we put it out of active maintenance, so it can still be easily forked and maintained by all who actively rely on it (as done by you).

If you want to revive and actively maintain this code base under the roof of the Eclipse foundation again, I do not object.

But to be clear, as of today there is no dedicated GEF-legacy project, there are just two different code bases in two different repositories, both belonging to the GEF project.

Also, there is no „ownership“ of an Eclipse project. The people actively involved in GEF can be found at https://projects.eclipse.org/projects/tools.gef/who. The respective rights and responsibilities, and how to get involved in a project is defined in the eclipse dev process (eclipse.org/projects/dev_process/). 

What would be your expectation regarding „GEF project ownership transfer“? Do you plan to actively contribute to the GEF project as a whole, or do you just feel obliged to GEF-legacy?

Best Regards,

Alexander

Am 16.02.2022 um 17:11 schrieb Serge Rider <serge@xxxxxxxxx>:

Hi Team!

I am from the DBeaver development team (https://dbeaver.io). We develop the universal database management tool based on the Eclipse RCP platform.
Besides other Eclipse RCP extensions, we heavily rely on legacy GEF/draw2d.

I was a speaker on several recent Eclipse Cons, the last session was about legacy GEF adoption:
https://www.eclipsecon.org/2021/sessions/diagrams-eclipse-rcp-back-future
https://www.youtube.com/watch?v=3ZIUB2XFDLE

What we want is to resurrect GEF3 maintenance and include it back to the standard Eclipse RCP lifecycle.
We have several PRs we'd like to merge in the codebase (currently we maintain all fixes in our forked repository on GitHub). We also want to propose legacy API improvements (keeping  API backward compatibility) and several features.

As far as I know, there are other groups of developers who eagerly want to contribute and/or maintain the GEF legacy project.

So, generally, the question is about the GEF project ownership transfer.

I don't know who owns the legacy GEF project.
If anyone can help us with this we would be really grateful.

Best regards,
Serge Rider
DBeaver CTO, developer

_______________________________________________
gef-dev mailing list
gef-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/gef-dev

Vorstand/Board: Jens Wagener (Vors./chairman), Dr. Stephan Eberle, Abdelghani El-Kacimi, Wolfgang Neuhaus, Franz-Josef Schuermann

Aufsichtsrat/Supervisory Board: Michael Neuhaus (Vors./chairman), Harald Goertz, Eric Swehla

Sitz der Gesellschaft/Registered Office: Am Brambusch 15-24, 44536 Lünen (Germany)

Registergericht/Registry Court: Amtsgericht Dortmund | HRB 20621

Attachment: signature.asc
Description: Message signed with OpenPGP