Bugzilla – Full Text Bug Listing
| Summary: | [proposal] tools.acute | ||
|---|---|---|---|
| Product: | Community | Reporter: | Stephanie Swart <stephanie.swart> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | akurtakov, lbullen, marcel.bruch, mistria, sharon.corbett, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-acute-c-and-.net-core-development-tools-eclipse-ide | ||
| Whiteboard: | |||
| Bug Depends on: | 519693 | ||
| Bug Blocks: | |||
|
Description
Stephanie Swart
We’ve received all of the project requirements and have scheduled the creation review to conclude on August 2, 2017. 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 Congratulations! Your project review is 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 Any news? I didnt't receive any request and neither did notifications about the GitHub repo being ready for migration. (In reply to Mickael Istria from comment #3) > Any news? I didnt't receive any request and neither did notifications about > the GitHub repo being ready for migration. Hi Mickael, currently several of our staff are away on holiday and therefore, there will be a slight waiting period. Thank you for your patience. 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=aCute Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/acute-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/acute.git Commits will be published to www.eclipse.org/acute within 5 minutes Downloads: http://download.eclipse.org/acute Archives: http://archive.eclipse.org/acute Builds: You can upload releases to ~committer_id/downloads/acute 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. 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 “checkin” 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 The CQ is now in the "checkin" state. Does that mean that the GitHub repo can already be migrated under the "eclipse" GitHub organization? (In reply to Mickael Istria from comment #6) > The CQ is now in the "checkin" state. Does that mean that the GitHub repo > can already be migrated under the "eclipse" GitHub organization? It can. Engage with the Webmaster to make it happen. https://wiki.eclipse.org/GitHub Unless there is something I'm missing, we're done here. Thanks! (In reply to Mickael Istria from comment #8) > Unless there is something I'm missing, we're done here. Thanks! For our own tracking purposes, we keep these bugs open until a project has done their first release. Thank-you. The project is up and running, we're done. |