Bugzilla – Full Text Bug Listing
| Summary: | [proposal] polarsys.capella | ||
|---|---|---|---|
| Product: | Community | Reporter: | Richard Burcher <richard.burcher> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | benoit.langlois, christophe.gatti, daniel.exertier, Ed.Merks, jean.barata, laurent.redor, matthieu.helleboid, mike.milinkovich, philippe.dul, stephane.bonnet, stepper, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | https://www.polarsys.org/proposals/capella | ||
| Whiteboard: | |||
| Bug Depends on: | 440806, 440807 | ||
| Bug Blocks: | |||
|
Description
Richard Burcher
FYI, The community can provide feedback in the following two locations; forum listing new project [1] and/or project proposal [2] [1] https://www.eclipse.org/forums/index.php/t/796387/ [2] https://www.polarsys.org/capella Hi Folks, Your projects creation review has not yet been scheduled. You can start thinking about and working on getting your initial code contribution put together. This will help speed up the project on-boarding process. Next Steps for the Project ========================== We will schedule the creation review once we have acquired the Trademark, 2 project mentors and two weeks of community review have passed. Interim Work The Project Can Do Before Creation Review ====================================================== Couple of items that you can get going on: - Please have your project leads and committers create Eclipse accounts [1], then log into [2]. This will help speed up the provisioning teams workflow to get all the projects resources in place quickly. - Please note, that the email addresses for committers in the proposal must match the email addresses associated with the Eclipse account. - The new project [3] can begin to assemble the projects initial code contribution [4]. Before you can make an initial contribution, your project needs to be provisioned. Getting the code ready now will reduce the time to submit the initial contribution once we've provisioned the project. Initial Code Contribution ------------------------- Broadly speaking, the initial code contribution involves: (this is a quick summary of [4]) - If applicable, update the package namespace. For example for Java based projects [5]. - Review "A Guide to the Legal Documentation for Eclipse-Based Content" [6] - Ensuring Eclipse copyright, license [7] and "about" notices [8]. - Identify all third-party party libraries. Other items to be aware of with the initial code contribution: - Code cannot be pushed to the project's source code repository until after the IP team has approved the initial Contribution. - The initial contribution must be the first commit in your project repository. History must be collapsed into that single commit [9]. - Any third-party libraries required by your code will have to be checked and approved by the IP Team. - Project-licensed content and third-party-licensed content are not reviewed together. Separate Contribution Questionnaires (CQ's) [10] are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [11] and the Parallel IP Process [12]. As an incubating project you can take advantage of Parallel IP to get moving quicker with development. Project Resources ================= Please have a look at the Development Resources wiki [13] and [14] the EDP process. Your project mentors are an excellent resource if you need guidance. We urge you to make use of their expertise. Cheers, Richard [1] https://dev.eclipse.org/site_login/createaccount.php [2] https://dev.eclipse.org/site_login/ [3] https://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project [4] http://wiki.eclipse.org/Development_Resources/initial_Contribution [5] https://wiki.eclipse.org/Development_Resources/HOWTO/The_Eclipse_Code_Namespace_Policy [6] https://www.eclipse.org/legal/guidetolegaldoc.php [7] https://www.eclipse.org/legal/copyrightandlicensenotice.php [8] https://www.eclipse.org/legal/epl/about.php [9] https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#Collapsing_History [10] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire [11] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [12] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [13] https://wiki.eclipse.org/Development_Resources [14] https://www.eclipse.org/projects/dev_process/development_process.php Thanks Richard, As requested, the commiters with no Eclipse account are going to create one shortly, and log in the Polarsys website. We'll keep you posted once done. Our initial contribution following all the expected rules is ready. We are just waiting for the Project creation and the provisioning. Given the fact that mentors are already identified, is it in the realm of possible to plan a Project creation review somewhere between August 18th and 22nd? Cheers, Stéphane (In reply to Stephane Bonnet from comment #3) > Thanks Richard, > > As requested, the commiters with no Eclipse account are going to create one > shortly, and log in the Polarsys website. We'll keep you posted once done. > > Our initial contribution following all the expected rules is ready. We are > just waiting for the Project creation and the provisioning. > > Given the fact that mentors are already identified, is it in the realm of > possible to plan a Project creation review somewhere between August 18th and > 22nd? > > Cheers, > > Stéphane That's great Stephane! We need the Trademark approve to come though and a minimum of two weeks of community review. Don't want to commit to anything and then not be able to deliver. The next available dates for review in August are the 13 or 27 and in September it's 10 or 24. Will keep you posted on the Trademark situation. Hi, Any news from the Trademarl approve? On our side, all committers' accounts are correctly settled. Any idea about when can we hope the Project Creation review? Thanks (In reply to Stephane Bonnet from comment #5) > Hi, > Any news from the Trademarl approve? > On our side, all committers' accounts are correctly settled. > Any idea about when can we hope the Project Creation review? > Thanks My apologies. I am responsible for initiating trademark reviews, and this slipped through the cracks. I have initiated the request. Capella creation review scheduled for September 10th and made public. Creation review successful. Project URL is: https://www.polarsys.org/projects/polarsys.capella Congratulations! Hi Folks, We have initiated the provisioning process for your project. Please watch your email for information and further instructions. This is a multi-step process that requires input from the project committers before we can do much else. Please complete the committer questionnaire and provide the requested committer documentation as soon as possible so that we can push forward. FYI === Let your new committers know that they won't be able to fill in their committer questionnaires until they have received their automated email titled "New Committer Request Form." A "project information" page [1] has been created that you can use to share information about the project with the community. As your committers are provisioned, they will be able to edit the information on this page. Next Steps for the Project ========================== The next step for the project will be the initial code contribution. While you're waiting for provisioning, you can start working on the initial contribution. [1] https://www.polarsys.org/projects/polarsys.capella Project has been provisioned by Webmaster. Please review comment 2 from the initial code contribution section onwards. If you have any questions, please don't hesitate to ask on the bug or email the EMO at <emo@eclipse.org>. Have a great weekend! We're reviewing it for sure, and we won't hesitate to contact the EMO if needed. Thanks Richard, and have a great weekend too! Hi, While attempting to elect new committers from portal ( https://dev.eclipse.org/portal/myfoundation/portal/portal.php ) the following error is raised: "Error! The project you are attempting to elect to is inactive." Checked with Philippe DUL, actual and only committer of the project. ( Cf. http://polarsys.org/projects/polarsys.capella/who ) What do we need to setup in order to "activate" the project so as to add committers ( all our development team in fact - see https://www.polarsys.org/proposals/capella at the bottom ) One more thing: I filled the Member Committer Questionnaire, but regarding people involved in Capella project and already Committer on Sirius project for instance, do they need to fill the Committer Questionnaire again for Capella ? ( in order to be granted with Committer rights ) Best regards, Christophe GATTI. (In reply to Christophe Gatti from comment #14) > Hi, > > > While attempting to elect new committers from portal ( > https://dev.eclipse.org/portal/myfoundation/portal/portal.php ) the > following error is raised: > > "Error! The project you are attempting to elect to is inactive." > > Checked with Philippe DUL, actual and only committer of the project. > ( Cf. http://polarsys.org/projects/polarsys.capella/who ) > > What do we need to setup in order to "activate" the project so as to add > committers ( all our development team in fact - see > https://www.polarsys.org/proposals/capella at the bottom ) > > > One more thing: I filled the Member Committer Questionnaire, but regarding > people involved in Capella project and already Committer on Sirius project > for instance, do they need to fill the Committer Questionnaire again for > Capella ? ( in order to be granted with Committer rights ) > > Best regards, > > Christophe GATTI. Hi Christophe, Project is now active; that was our mistake - sorry. You should now be able to run the election. In regards to the second question, yes they will need to fill out the Committer Questionnaire. Have a good one:) Richard Capella is working on their second release. I believe that we can reasonably consider the project fully operational and close this tracking bug. |