Bugzilla – Full Text Bug Listing
| Summary: | [proposal] polarsys.polarsys.opencert | ||
|---|---|---|---|
| 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: | angel.lopez, cydnie.smith, gael.blondelle, huascar.espinoza, stephanie.swart |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://www.polarsys.org/proposals/opencert | ||
| Whiteboard: | |||
| Bug Depends on: | 483494, 483495 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Mike has expressed concern that the name, OpenCert, is suggestive of digital certificates. Do you share this concern? Embedded systems people (the target of PolarSys), think certification when they read "cert". So I think that as the project will be hosted by PolarSys, it will be clear that it is about certification and not about certificates. I still require a mentor. In anticipation of being successful in my search for a mentor, I've scheduled the creation review to conclude on December 16/2015. 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 must be completed. The exact nature of that paperwork depends on several factors, including the employment status on the individual and the Eclipse Foundation membership status of the employer. More information: https://www.eclipse.org/projects/handbook/polarsys.html#paperwork 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. I declare this 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). Immediately following the provisioning process, your next step will be 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. In anticipation of this step, you may consider ensuring that your code has the required copyright headers and namespace (if applicable). If you have any questions, please send a message to emo@eclipse.org and we will provide assistance. Please encourage all project committers to join the incubation mailing list [3]. 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. An overview of the complete project creation process is in the Project Handbook [4]. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution [3] https://dev.eclipse.org/mailman/listinfo/incubation [4] https://www.eclipse.org/projects/handbook/#starting Greetings project team, It looks like your initial contribution was approved and you have no open CQs; however, it looks like there have been no releases planned. What is the status of this project and your first release? Is there anything we can assist with? For more information on the release process, please check out our handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release (In reply to Cydnie Smith from comment #5) > Greetings project team, > > It looks like your initial contribution was approved and you have no open > CQs; however, it looks like there have been no releases planned. What is the > status of this project and your first release? Is there anything we can > assist with? > > For more information on the release process, please check out our handbook > [1]. > > [1] https://www.eclipse.org/projects/handbook/#release Dear Cydnie, The European Project that was generating Eclipse Opencert finished on March, therefore we have no plan of updating the code with new features. This is something that we have to discuss internally. What kind of documentation is needed for the release review by the PMC? Regards, Angel. (In reply to Angel Lopez from comment #6) > (In reply to Cydnie Smith from comment #5) > > Greetings project team, > > > > It looks like your initial contribution was approved and you have no open > > CQs; however, it looks like there have been no releases planned. What is the > > status of this project and your first release? Is there anything we can > > assist with? > > > > For more information on the release process, please check out our handbook > > [1]. > > > > [1] https://www.eclipse.org/projects/handbook/#release > > > Dear Cydnie, > > The European Project that was generating Eclipse Opencert finished on March, > therefore we have no plan of updating the code with new features. > > This is something that we have to discuss internally. > > What kind of documentation is needed for the release review by the PMC? The EMO looks for a paragraph that describes the release; though, the PMC may require more. More details about the release process, such as providing release materials, are in the handbook. Thanks, Cydnie > > Regards, > > Angel. |