-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename gef-legacy to gef-classic #5
Comments
As in GEF5 gef fx is just one feature of the whole GEF 5 suite I find gef-swt to limiting in scope. How about gef-classic? |
@azoitl sounds also fine for me Any other opinions? |
|
@mwienand can you approved as project lead? |
Sounds good to me. Btw, GEF Classic reminds me of OPC Classic. |
Done, thanks. @mwienand do you if we have an active build job for the old legacy repo which we need to update? |
Maybe that's where I got the inspiration from ;-) |
gef-legacy gives a very negative feeling about the project. I suggest we rename it to gef-swt.
The text was updated successfully, but these errors were encountered: