Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ecd.theia | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alex.tugarev, anton, cydnie.smith, gunnar, malaperle, marc.dumais, sharon.corbett, sven.efftinge, thabang.mashologu, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-theia | ||
| Whiteboard: | |||
| Bug Depends on: | 533590, 533882 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
My apologies: I just noticed that the requested licensing scheme is different from what is preapproved for the Top Level Project. I've opened Bug 533882 to track the required board approval. Sven and Marc, we require your input there, please. We’ve received all of the project requirements and have scheduled the creation review to conclude on May 2/2018. Please continue to monitor communication channels. Following the creation review, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [1] must be completed. The exact nature of that paperwork depends on several factors, including the employment status of the individual and the Eclipse Foundation membership status of the employer. If you can be ready with the paperwork in time for the completion of the creation review, then we can move quickly through the provisioning process. When we initiate provisioning, committers will be sent an email with instructions; please don't send any paperwork in until after you receive those instructions. Please encourage all future project committers to join the incubation mailing list [2]. We use this list to connect committers from new projects to their peers in other projects in the incubation phase and to mentors who can help answer questions and discuss issues related to the project onboarding process. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://dev.eclipse.org/mailman/listinfo/incubation I declear the Creaton Review successful! We will initiate the project resources provisioning process shortly. Please tell your project committers to carefully monitor their email for a message from The Eclipse Foundation with instructions for providing committer paperwork [1]. Our IT team cannot allocate project resources until after we have processed the paperwork for at least one committer, so your attention in this matter will keep the process moving forward. Be advised that the paperwork process will time out after 120 days; any committers who are unable to complete their paperwork requirements in this timeframe will have to be elected to the project (your project mentors can provide assistance with this). [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization and flatten any previous history. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=theia Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/theia-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/theia.git Commits will be published to www.eclipse.org/theia within 5 minutes Downloads: http://download.eclipse.org/theia Archives: http://archive.eclipse.org/theia Builds: You can upload releases to ~committer_id/downloads/theia via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required. (In reply to Eclipse Webmaster from comment #4) > Issue Tracker: > > https://bugs.eclipse.org/bugs/describecomponents.cgi?product=theia I think the issue tracker is supposed to be Github and the product removed should be removed from Bugzilla. Otherwise, there will be confusion for bug reporters. (In reply to Marc-André Laperle from comment #5) > I think the issue tracker is supposed to be Github and the product removed > should be removed from Bugzilla. Otherwise, there will be confusion for bug > reporters. Done. -M. Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “check in” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution (In reply to Wayne Beaton from comment #7) > Your next step is to submit an initial contribution [1] for review by the IP > Team. Hi Wayne, Can this be done while we are finishing gathering contributor's permissions, to re-license their respective contributions? (In reply to Marc Dumais from comment #8) > (In reply to Wayne Beaton from comment #7) > > Your next step is to submit an initial contribution [1] for review by the IP > > Team. > > Hi Wayne, > > Can this be done while we are finishing gathering contributor's permissions, > to re-license their respective contributions? No. Please wait until you have that exercise complete. My apologies if I've confused you. Posting this message is the next step in our process and I just did it automatically as part of a bunch of bulk updates (without recalling that you were engaged in that process). (In reply to Wayne Beaton from comment #9) > No. Please wait until you have that exercise complete. ok, thanks for the quick answer. The relicensing exercise is now complete subject to the removal of commits by the following two contributors as agreed upon with the project: daveyc123 moondef Regards, S. Corbett We intend to move the repository [] to the eclipse organization. Can we do it like this: 1) Create a new branch, with a squashed and relicensed state of master, that has the two commits for which we don't have approval removed. 2) Create a CQ, pointing to that branch and wait for approval. 3) Move the repo to eclipse organization I understood that we could add new commits with 'sign-off' messages done by committers. Is that correct in the meantime? (In reply to Sven Efftinge from comment #12) > We intend to move the repository [] to the eclipse organization. > Can we do it like this: > > 1) Create a new branch, with a squashed and relicensed state of master, that > has the two commits for which we don't have approval removed. > 2) Create a CQ, pointing to that branch and wait for approval. > 3) Move the repo to eclipse organization The webmaster has a well defined process. https://wiki.eclipse.org/GitHub > I understood that we could add new commits with 'sign-off' messages done by > committers. Is that correct in the meantime? You can add new commits (I assume that you mean after passing the initial contribution to the IP Team). There's no need for current committers to "sign-off". Contributions made by anybody who is not a current committer need to be signed-off and the person must have signed the ECA. Hi, thanks for the link. I will start preparing the initial contribution including removing commits from daveyc123, moondef, and applying Eclipse copyright and license notice(s). For now i will do it in a separate branch. As it is finished we can start using the branch as master, tag as `eclipse_initial` and submit it for the review. All new commits will have to be under Eclipse copyrights since then. > You can add new commits (I assume that you mean after passing the initial contribution to the IP Team).
I meant that we would create a branch and a tag it. That tag points to the to be approved state. We will create a CQ with that state, pointing to the tag.
We would keep working during the review but using the new license and by applying to the Eclipse contribution guidelines.
Later when the state is approved and we move the repository and create the one big 'initial contribution' commit, we would rebase the additional commits on top of it keeping the history of them, since they were done based on the new rules and license.
This way we would not have to stop development. Would that work?
The description in [1] seems to positively answer what I am asking. [1] - https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#Processing_Repositories (In reply to Sven Efftinge from comment #16) > The description in [1] seems to positively answer what I am asking. Agreed. (In reply to Sven Efftinge from comment #15) This is what I tried to say. Do this. It looks like "Check in" has been received but no release has been scheduled. What are your plans for release? Theia Project: Please ignore the question raised in Comment #18. Unfortunately, we have not informed Cydnie of the ongoing IP work which prevents the project from being able to answer the question. Apologies folks! Thanks, Sharon Project has engaged in its first release! I declare this project fully operational. This bug is now closed. (In reply to Cydnie Smith from comment #20) > Project has engaged in its first release! I declare this project fully > operational. This bug is now closed. Awesome, thanks Cydnie. |