You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I had more time for this project than I have now, there was a private email thread which investigated if it would be possible to move this repository from here to eclipse.org. The outcome was that it was feasible and eclipse.org would be open to it.
I never followed-up on that - would anyone else be interested to take over getting this done? I could find the old email thread and forward it to anyone interested in taking this on. ou probably need to already be set up on eclipse.org though.
Hi @vorburger,
the point for me is not "interested" or "not interested".
Its the lack of free spare time.
What's the advantages for you if the project is an Eclipse project?
It is about EEA, so license problems etc. should not really matter.
If everyone that needs to contribute a few lines of EEA needs to sign a ECA / CLA wouldn't this be to complicated?
What do you think will be "easier to be done" (for EEAs) in an Eclipse project than in a private one?
I totally agree re. remaining on GitHub. The thinking was that perhaps it
could move to GitHub.com/eclipse/... instead of here in our org.
Advantage would include Eclipse.org CLA verification.
It's not something I have the time to drive either, but I thought having an
open issue just in case someone else would ever like to get involved here
can't hurt.
When I had more time for this project than I have now, there was a private email thread which investigated if it would be possible to move this repository from here to eclipse.org. The outcome was that it was feasible and eclipse.org would be open to it.
I never followed-up on that - would anyone else be interested to take over getting this done? I could find the old email thread and forward it to anyone interested in taking this on. ou probably need to already be set up on eclipse.org though.
@maggu2810 @kwin @ctron @brychcy @sylvainlaurent
The text was updated successfully, but these errors were encountered: