Thanks a lot Wayne!
@Marc, by fulfilling the condition below stated by Wayne you have my:
+1
Congrats!
Regards,
Nedelcho
From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Date: Monday, 22 July 2019, 5:41
To: Marc Dumais <marc.dumais@xxxxxxxxxxxx>
Cc: Eclipse cloud development PMC discussions <ecd-pmc@xxxxxxxxxxx>, "Delchev, Nedelcho" <nedelcho.delchev@xxxxxxx>, "emo-ip-team@xxxxxxxxxxx" <emo-ip-team@xxxxxxxxxxx>, "emo@xxxxxxxxxxxxxxxxxxxxxx" <emo@xxxxxxxxxxxxxxxxxxxxxx>, Sharon Corbett <sharon.corbett@xxxxxxxxxxx>,
Gorkem Ercan <gercan@xxxxxxxxxx>
Subject: Re: [ecd-pmc] Request assistance for Eclipse Theia: approval for release 0.9.0
I spoke briefly with Marc on Friday. The project team's primary concern is that the project be able to maintain a rapid release cadence.
We made some changes to the Eclipse Development Process in late 2018 which help. Specifically, we made a change that permits a project to engage in releases for an entire year following a successful release review. We also introduced the
notion of a "progress review" which is, essentially, the same thing as a release review, but without being aligned with a release.
A project can, for example, engage in a weekly release cadence, so long as the team engages in a progress review at least once every year (and the project can even engage in releases while a progress review is... well... in progress). Think
of the progress review as an opportunity to confirm that the project is following the rules and engaging in the right sorts of activities to be a successful Eclipse open source project.
The IP Policy is still in effect. Every release many only include intellectual property that has been fully vetted and approved by the IP Due Diligence process.
Given that the project has been following the rules in every way except having the repositories moved to Eclipse Foundation control, I recommend that the PMC approve this release review on condition that the project team:
-
Grant the Eclipse Webmaster (@eclipsewebmaster) administrator privileges on the Git repository;
-
Commit to moving the repository before September 15;
-
Ensure that the Git Repository conforms to all Eclipse Foundation branding guidelines; and
-
Resubmit the IP Log.
I'll ask the Webmaster to wait to move the repository until after requested by the project team.
Regarding branding, the project name needs to be "Eclipse Theia" in the first and all prominent occurrences, add an indication that "Theia" is a trademark of the Eclipse Foundation in the README, and include a link to
https://www.eclipse.org/theia.
I've connected the repository into the IP Log Generator. You should only have to
regenerate and resubmit the log.
What we likely agreed to was that the project would continue to do releases outside of the Eclipse Development Process while engaged in the onboarding process. An official Eclipse Development Process release with the source code in a repository
that's not hosted by the Eclipse Foundation is unprecedented.
My understanding is that all of the outstanding IP issues have been resolved. It appears that the repository has the necessary legal documentation in place, and that the project team is taking care to ensure that all contributors have signed
the ECA and are signing-off their contributions.
Other than the fact that the repository hasn't been migrated into an Eclipse Foundation organization, I don't see anything that will prevent the project from pushing out an incubation release.
I need to sort out whether or not this is an invalid intermediate state that the EMO can support. It would certainly help me to decide if you could be more specific than "probably after summer vacations" regarding the timing of the migration.
Are there other issues need to be resolved before you can move the repository?
Hi Nedelcho,
In the case of Eclipse Theia, we have a chicken-and-egg type situation: before moving the repo under Foundation control, we want to make sure we are able to release, as part of the Foundation, to avoid delaying releases
and risk impacting project adoption.
I had a meeting in early April, with Sharon, Wayne and Gorkem, where we discussed the way forward. Though it was not required by the Foundation, I believe that it was agreed
that we could go ahead with one of our monthly release, using the Foundation's process, before moving our repository. The plan was just delayed a bit to iron-out a couple of new IP issues that were noticed around that time.
Note that even if the main project's repo has not yet moved under Foundation control, the most recent state (master) has been subject to the Foundation's IP processes, such that no un-analysed content, that pre-dates
the project's initial contribution, should be part of the release.
Regards,
Marc
On 2019-07-18 4:33 a.m., Delchev, Nedelcho wrote:
Hi,
Including EMO as their statement here is required. As far as I remember all the official Eclipse projects have to be under the "eclipse" organization in GitHub and have to start with a clean repository.
Regards,
Nedelcho
On 18.07.19, 0:40, "ecd-pmc-bounces@xxxxxxxxxxx on behalf of Gorkem Ercan" <ecd-pmc-bounces@xxxxxxxxxxx on behalf of gorkem.ercan@xxxxxxxxx> wrote:
Marc,
Can you remind me with this release, will Theia be able to move its
repository to Eclipse foundation?
Thanks,
Gorkem
On 17 Jul 2019, at 15:11, Marc Dumais wrote:
> Hi,
>
> I was told to seek PMC approval for the project's 0.9.0
> release<https://projects.eclipse.org/projects/ecd.theia/releases/0.9.0>
> material.
>
> Release review:
> https://projects.eclipse.org/projects/ecd.theia/reviews/0.9.0-release-review
>
> Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546663
>
> Please let me know if there is other information I can provide.
>
> Thanks,
>
> Marc
>
>
> _______________________________________________
> ecd-pmc mailing list
> ecd-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ecd-pmc
_______________________________________________
ecd-pmc mailing list
ecd-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ecd-pmc
_______________________________________________
ecd-pmc mailing list
ecd-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ecd-pmc
--
Wayne Beaton
Director of Open Source Projects |
Eclipse Foundation, Inc.
--
Wayne Beaton
Director of Open Source Projects |
Eclipse Foundation, Inc.
|
