Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.arrowhead | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Maria Teresa Delgado <mariateresa.delgado> | ||||
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jerker.delsing, marco.jahn, philippe.krief, pvarga, sharon.corbett, szvetlin, wayne.beaton, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X | ||||||
| URL: | https://projects.eclipse.org/proposals/eclipse-arrowhead | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 561963, 561964, 569115 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Maria Teresa Delgado
I have scheduled the creation review to conclude on May 20th 2020. 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 declare the Creation 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). The next step is to submit an initial contribution [2] 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. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [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. This work can begin as soon as you have check in permission from EMO legal.
Issue Tracker:
Github issues will be enabled for your project.
Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/arrowhead-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/arrowhead.git
Commits will be published to www.eclipse.org/arrowhead within 5 minutes
Downloads: http://download.eclipse.org/arrowhead
Archives: http://archive.eclipse.org/arrowhead
Builds: You can upload releases to ~committer_id/downloads/arrowhead 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.
-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. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution Created attachment 283353 [details]
Only the source code is attached and the readme, without third party files and documentation
Initial Contribution
Dear Szvetlin, for the initial contribution you need to create a CQ using the committer tools. More information is available in the handbook: https://www.eclipse.org/projects/handbook/#ip-initial-contribution we remain available for any doubts you might have. Maria Teresa Dear Maria, I've already submitted the CQ. https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22299 Best wishes, Svetlin great! Your initial contribution has been approved by the IP Team! You may now begin pushing source code into Eclipse project repositories. If this content is in a GitHub repository, the Eclipse Webmaster can help you move that repository into an Eclipse Foundation-managed GitHub Organization. Alternatively, the webmaster can help you create a new repository in GitHub, or the Eclipse Foundation’s GitLab or Gerrit. Open an issue against Community/Git to request Eclipse Webmaster assistance. The next step is to start thinking about a release date [1] for your project. Project release dates should be as realistic as possible (usually 6 or more weeks after your IP request receives check in). Once you have decided on a release date, the next step is to create a release record with that date. Release dates may be updated or revised to reflect project progress. Projects may not be released until intellectual property is approved by IP Team. [1] https://www.eclipse.org/projects/handbook/#release Ping The project team has requested transfer of their initial contribution from their existing github repo to the new Eclipse-managed organisation: https://bugs.eclipse.org/bugs/show_bug.cgi?id=569115 One CQ regarding third-party license check is still open: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22783 The project is up and running. I'm marking this as fixed. The next step for the project team is to engage in their first release and corresponding release review. There is more information and help in the handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release |