Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.ease | ||
|---|---|---|---|
| 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: | arthur.daussy, chris.guindon, christian.pontesegger, denis.roy, marcel.bruch, sharon.corbett, stepper, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-advanced-scripting-environment-ease | ||
| Whiteboard: | |||
| Bug Depends on: | 433396, 433397 | ||
| Bug Blocks: | |||
|
Description
Richard Burcher
Bugzilla not accepting one of the committers email addresses for CC. >>Bugzilla was unable to make any match at all for one or more of the names and/or email addresses you entered on the previous page. >>Please go back and try other names or email addresses. Need to look into. (In reply to richard burcher from comment #1) > Bugzilla not accepting one of the committers email addresses for CC. That means that the committer doesn't have an Eclipse Foundation account. I recommend sending them a short note inviting them to create an account and add themselves to the CC list. Thanks, Have emailed requesting account signup with instructions and for user to add self to bug here. Arthur changed the company recently. He might be signed up with his old address at eclipse This has been resolved. Arthur has updated the email account on cc. 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 project on-boarding process. Next Steps for the Project ========================== Project creation review to be scheduled. Interim Work The Project Can Do Before Creation Review ====================================================== In the interim the new project [1] can begin to assemble the projects initial code contribution [2] to be ready for the Provisioning phase (we undertake this on behalf of the projects now). 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 [2]) - Updating the package namespaces to either org.eclipse.<project-name> or org.locationtech.<project-name> depending on the projects forge location. - Ensuring Eclipse copyright and license notices are present. - All required notices are present. - Ensure that no nesting of source files is present. - Identify and remove all third-party party libraries from the source code. 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. - 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) are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [3] and the Parallel IP Process [4]. 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 [5] and [6] 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://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project [2] http://wiki.eclipse.org/Development_Resources/initial_Contribution [3] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [4] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [5] https://wiki.eclipse.org/Development_Resources [6] https://www.eclipse.org/projects/dev_process/development_process.php EASE code is currently in the e4 project. I assume that it's in a separate Git repository. We will confirm with the IP Team, but... an initial contribution is most likely not required since the existing code base is already in an Eclipse project and authored by Eclipse committers. As we get ready for provisioning, we do need to assemble the list of CQs that either need to be moved out of e4 (because they're specific to EASE) or be piggybacked (because they're needed both by e4 and by EASE). (In reply to Wayne Beaton from comment #7) > I assume that it's in a separate Git repository. Correct, We have our own repository @ org.eclipse.e4.scripting.master > an initial > contribution is most likely not required since the existing code base is > already in an Eclipse project and authored by Eclipse committers. Since our initial commit at e4 we had additions from the 2 main committers and one from a contributor who provided code via gerrit (and obviously had signed his CLA) I will check for the disclaimers in all the added files. Might be the case we missed some of them in the last months. Project as 2 mentors. Have updated proposal in PMI to reflect new mentors. Creation review scheduled for June 18. Hi Folks, Your projects creation review has been scheduled. Next Steps for the Project ========================== Project provisioning to provide all the infrastructure and resources for the project. We will take care of provisioning for you once the project is created. Information We Need ------------------- - What type of Git repository does the project want. Github based (under one of the forges) [1] or regular Git repository hosted on Eclipse infrastructure? - If you've selected using a Github repository for the above question, will you be moving an existing Github project? If so please provide the full urls. Interim Work The Project Can Do Before Creation Review ====================================================== Couple of items you can get going on: - Please have your project leads and committers create Eclipse accounts [2], then log into [3]. This will help speed up the provisioning teams workflow to get all the projects resources in place quickly. - The new project [4] can begin to assemble the projects initial code contribution [5] to be ready for the Provisioning phase (we undertake this on behalf of the projects now). 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 [5]) - Updating the package namespaces to either org.eclipse.<project-name> or org.locationtech.<project-name> depending on the projects forge location. - Ensuring Eclipse copyright and license notices are present. - All required notices are present. - Ensure that no nesting of source files is present. - Identify and remove all third-party party libraries from the source code. 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. - 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) are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [6] and the Parallel IP Process [7]. 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 [8] and [9] 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://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub [2] https://dev.eclipse.org/site_login/createaccount.php [3] https://dev.eclipse.org/site_login/ [4] https://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project [5] http://wiki.eclipse.org/Development_Resources/initial_Contribution [6] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [7] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [8] https://wiki.eclipse.org/Development_Resources [9] https://www.eclipse.org/projects/dev_process/development_process.php Project has been successfully created after creation review. 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. Initial Code Contribution ------------------------- Broadly speaking, the initial code contribution involves: (this is a quick summary of [2]) - If applicable, update the package namespace. For example for Java based projects [3]. - Ensuring Eclipse copyright, license [4] and "about" notices [5]. - 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 [6]. - 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) [7] are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [8] and the Parallel IP Process [9]. 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 [10] and [11] 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://projects.eclipse.org/projects/technology.ease [2] http://wiki.eclipse.org/Development_Resources/initial_Contribution [3] https://wiki.eclipse.org/Development_Resources/HOWTO/The_Eclipse_Code_Namespace_Policy [4] https://www.eclipse.org/legal/copyrightandlicensenotice.php [5] https://www.eclipse.org/legal/epl/about.php [6] https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#Collapsing_History [7] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire [8] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [9] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [10] https://wiki.eclipse.org/Development_Resources [11] https://www.eclipse.org/projects/dev_process/development_process.php I've just updated all the file headers and copyright notices. Hope we are clean right now regarding that. Is there any action I should take to advance for the initial code contribution? If we could just move the current e4 repo this would be great. We also could simply start with the latest commit in master. Anything I can do regarding the CQs (see comment 7)? (In reply to Christian Pontesegger from comment #14) > I've just updated all the file headers and copyright notices. Hope we are > clean right now regarding that. > > Is there any action I should take to advance for the initial code > contribution? If we could just move the current e4 repo this would be great. > We also could simply start with the latest commit in master. Sharon, the EASE project comes from code originally created in the e4 incubator project by existing committers in accordance with the Eclipse IP Policy. Do you have any concerns with them just moving their existing Git repository into the new project without submitting an initial contribution for review? > > Anything I can do regarding the CQs (see comment 7)? Please provide a list of CQs that can be moved from e4 to EASE. A CQ can be moved if it is only required by the EASE code and is no longer required by the e4 project. For CQs that are required by EASE, but need to stay with e4, please open piggyback CQs. Let us know if you require further explanation or assistance. (In reply to Wayne Beaton from comment #15) > Please provide a list of CQs that can be moved from e4 to EASE. A CQ can be > moved if it is only required by the EASE code and is no longer required by > the e4 project. CQ 7623 .. initial contribution CQ 7653 .. Jython (works with) > For CQs that are required by EASE, but need to stay with e4, please open > piggyback CQs. Let us know if you require further explanation or assistance. CQ 7644 .. Rhino Seems I cannot open a new CQ topic. I am redirected to the portal: "The Contribution Questionnaire has been moved to the portal" but cannot find it there. (In reply to Christian Pontesegger from comment #16) > Seems I cannot open a new CQ topic. I am redirected to the portal: "The > Contribution Questionnaire has been moved to the portal" but cannot find it > there. Look for the "Projects" component. Click "[view]" next to "technology.ease". There you'll see "[use] a third-party library from Orbit" Got to wait for project creation to be done as I cannot file CQs before that (see bug 437741) Project has been provisioned. Hi Folks, The project has now been provisioned. Next Steps for the Project ========================== The next step for the project will be the initial code contribution. We use a modified version of Bugzilla that we call IPZilla [1] intellectual property contributions for projects. This is only accessible to committers. Individual contribution records are called Contribution Questionnaire (CQ's) [2] . A CQ is required for the projects initial contribution and all third party libraries. Broadly speaking, the initial code contribution involves: (this is a quick summary of [3]) - If applicable, update the package namespace. For example for Java based projects [4]. - Review "A Guide to the Legal Documentation for Eclipse-Based Content" [5] - Ensuring Eclipse copyright, license [6] and "about" notices [7]. - 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 [8]. - 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) [2] are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [9] and the Parallel IP Process [10]. 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 [11] and [12] the EDP process. Your project mentors are an excellent resource if you need guidance. We urge you to make use of their expertise. Thanks and let me know if you have any questions, Richard [1] https://wiki.eclipse.org/IPzilla [2] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire [3] http://wiki.eclipse.org/Development_Resources/Initial_Contribution [4] https://wiki.eclipse.org/Development_Resources/HOWTO/The_Eclipse_Code_Namespace_Policy [5] https://www.eclipse.org/legal/guidetolegaldoc.php [6] https://www.eclipse.org/legal/copyrightandlicensenotice.php [7] https://www.eclipse.org/legal/epl/about.php [8] https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#Collapsing_History [9] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [10] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [11] https://wiki.eclipse.org/Development_Resources [12] https://www.eclipse.org/projects/dev_process/development_process.php Initial contribution submitted: bug 438498 CQ submitted. Parallel IP approved on 10 July 2014. Hi Folks, Your project has received Parallel-IP check-in approval from the IP Team for the initial code contribution. Next Steps for the Project ========================== Commit the projects approved initial contribution into the projects repository. Please note that history must be collapsed into that single commit. If you have any questions pertaining to the repository or collapsing the history, please contact the Webmaster <webmaster@eclipse.org>. Important: Legal ================ The Parallel IP process allows the check-in to occur before the full legal review is complete (but after preliminary legal approval). The full legal review must be completed before the code is included in a release. Please review "A Guide to the Legal Documentation for Eclipse-Based Content" [1]. This is an ongoing process for the project. Accepting Code ============== The IP Due Diligence Process [2] is an on going process and needs to be followed closely. Contributors ------------ Please review [3] on how to handle code submissions. Committers ---------- FYI [4]. For Projects Hosted on GitHub ------------------------- Please review hosting a project on GitHub [5] and social coding FAQ's [6]. Project Resources ================= Please have a look at the Development Resources wiki [7], [8] the EDP process and Contribution License Agreement (CLA) [9]. Your project mentors are an excellent resource if you need guidance. We urge you to make use of their expertise. Cheers, Richard [1] https://www.eclipse.org/legal/guidetolegaldoc.php [2] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [3] https://wiki.eclipse.org/Development_Resources/Contributing_via_Git [4] https://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions [5] https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub [6] https://www.eclipse.org/org/SocialCodingFAQ.php [7] https://wiki.eclipse.org/Development_Resources [8] https://www.eclipse.org/projects/dev_process/development_process.php [9] https://wiki.eclipse.org/CLA first: thanks for your support here I am trying to find information on how to modify the ease project webpage and transform it to something like the tycho site. Any (wiki) info available how to do this? Websites are stored in git. The tycho site is here [1]. However, I'd suggest to rather go with the EGIT project site which integrates into the new look-and-feel at eclipse.org [2]. I don't know whether there is any up-to-date wiki documentation. [1] http://git.eclipse.org/c/www.eclipse.org/tycho.git/tree/ [2] http://git.eclipse.org/c/www.eclipse.org/egit.git/tree/ thanks marcel, I was just investigating the recommenders web page code :) Is there a way to test changes before uploading them? It was possible (but quite complicated) to setup the old system on a local webserver. I can't make any statements about the latest templates of the EF. Using your own home-brewed templates with php/bootstrap will probably be the simplest to set up. But maybe one of the website masters can comment? (In reply to Christian Pontesegger from comment #26) > Is there a way to test changes before uploading them? There is a staging mechanism in place. I don't find the original announcement but bug 436939 might provide some pointers. // Webmaster Can you please help on Comment 26. If you have a web server running locally, you should be able to test locally too. Alternativelu, you can push to a branch called "staging" and the content will be available on our staging server: http://staging.eclipse.org Once you're done staging, push to the master branch and the content will be picked up by www.eclipse.org. (In reply to Christian Pontesegger from comment #26) > thanks marcel, I was just investigating the recommenders web page code :) > > Is there a way to test changes before uploading them? Maybe we should spend some time on a Docker image that would setup a local web server for Eclipse projects? That sounds like a good idea. Hi Folks, Besides raising [1] a Contribution Questionnaire (CQ's) for the projects initial code contribution, you must also raise CQ's for every third-party library [2] that your project code makes direct use of. Please review our guidelines for 3rd Party Dependencies [3]. Please first discuss with your Mentors and/or PMC if you have any questions. Thanks and let me know if you have any questions, Richard [1] https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire [2] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire#Third_Party_Libraries [3] https://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf thanks for pointing me to the staging area. Raised bug 440950 for a permanent solution in case the staging area is shut down in the near future. EASE is working on their first release. I think that we can reasonably declare victory on the proposal. Congratulations and welcome! |