Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.che | ||
|---|---|---|---|
| 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: | denis.roy, dmi3.kuleshov, gazarenkov, marcel.bruch, mik, richard.burcher, sharon.corbett, tylerjewell, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | https://projects.eclipse.org/proposals/che | ||
| Whiteboard: | |||
| Bug Depends on: | 438824, 438825 | ||
| Bug Blocks: | |||
|
Description
Richard Burcher
project name updated to "Che". updated project name at these locations: - proposal url - eclipse forums - all references within proposal projects has 2 mentors. Creation review scheduled for July 30. Creation review successful, congratulations and welcome to Eclipse! Requested project provisioning. Project link in PMI is: https://projects.eclipse.org/projects/technology.che 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]. - Review "A Guide to the Legal Documentation for Eclipse-Based Content" [4] - Ensuring Eclipse copyright, license [5] and "about" notices [6]. - 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 [7]. - 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) [8] 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. Cheers, Richard [1] https://projects.eclipse.org/projects/technology.che [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/guidetolegaldoc.php [5] https://www.eclipse.org/legal/copyrightandlicensenotice.php [6] https://www.eclipse.org/legal/epl/about.php [7] https://wiki.eclipse.org/Social_Coding/Hosting_a_Project_at_GitHub#Collapsing_History [8] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire [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 Project has been provisioned. Provisioning Comments from Webmaster email below. Putting here as a public findable resource for the project and those involved. =============== Greetings, The Che project is all set up and ready to go! Here are the specifics (please communicate this information to your committers): ** Please note: If I was unable to locate committer records for some of the initial committers they won't be able to access the resources below until they receive their eclipse.org user id's. 1.GIT access: 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. As your project is now an Eclipse Foundation project, please observe and follow the Eclipse Committer Due Diligence guidelines explained below: http://www.eclipse.org/legal/committerguidelines.php If you have any questions with regards to the operation of your project or the above guidelines, please don't hesitate to contact webmaster@eclipse.org (Infrastructure issues) or emo@eclipse.org (Process/guidelines issues). 2. Build Services We encourage Eclipse projects to make use of the common build infrastructure we provide. See: http://wiki.eclipse.org/CBI for details. 3. Project Website Your project website is up and ready to be authored. Simply set up a new repository location: host: git.eclipse.org repository: /gitroot/www.eclipse.org/che.git Anything you commit to che.git will be automatically published to http://www.eclipse.org/che/ within one minute. We have set up a sample web page which can be viewed at http://www.eclipse.org/che 4. Mailing lists The che-dev@eclipse.org list has been created. You can subscribe to the list here: https://dev.eclipse.org/mailman/listinfo/che-dev . Subscription is required to post messages to the list. 5. Newsgroups & Forums The eclipse.che newsgroup has been created on the news.eclipse.org server. This news group is linked to the forums hosted here: www.eclipse.org/forums/index.php/f/ If you need additional mailing lists or newsgroups, please contact webmaster@eclipse.org 6. Downloads You have a downloads area with 2GB of space. To access this area, simply use an SFTP or SCP client (such as CoreFTP or WinSCP) in SSH mode to and connect to build.eclipse.org. Your downloads path can be accessed 2 ways: ~committerid/downloads/che -or- /home/data/httpd/download.eclipse.org/che Please be conservative when transferring files: the downloads area is mirrored to over 70 mirror sites worldwide. To link to a downloadable file, use the following path: <a href="http://www.eclipse.org/downloads/download.php?file=/che/che-1.0.0.zip"> This will ask users to pick a mirror site for the file, and it will add che downloads to our download statistics (also in the Committer Tools, Live Download Stats). You can move any outdated or un-needed files to archive.eclipse.org just by copying the files to /home/data/httpd/archive.eclipse.org/che . 7. Bugzilla Your bugzilla project, components, versions (if specified) and milestones (if specified) have been created. If your committers had a bugzilla account that matches the e-mail address supplied to the Foundation, their account was granted standard committer rights to edit and confirm bugs. If the committers didn't have a bugzilla account, they should create one using the same e-mail address as supplied to the Foundation and contact webmaster@eclipse.org to have their account upgraded with committer rights. If you have any questions, or if you need assistance in using any of the resources, please don't hesitate to drop me a line. -Matt. ============ 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] [2] intellectual property contributions for projects. This is only accessible to committers. Individual contribution records are called Contribution Questionnaire (CQ's) [3] . 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 [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) [3] are required. Important: Legal ================ Please familiarize yourself with the IP Due Diligence Process [10] and the Parallel IP Process [11]. 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 [12] and [13] 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://dev.eclipse.org/ipzilla/ [3] https://wiki.eclipse.org/Development_Resources/Contribution_Questionnaire [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] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf [11] http://www.eclipse.org/projects/dev_process/parallel-ip-process.php [12] https://wiki.eclipse.org/Development_Resources [13] https://www.eclipse.org/projects/dev_process/development_process.php 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 check Orbit (repository of bundled versions of third party libraries that are approved for use in one or more Eclipse projects) [3][4] to see the library is present. Please review our guidelines for 3rd Party Dependencies [5]. 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/orbit/ [4] http://download.eclipse.org/tools/orbit/downloads/ [5] https://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf We have checkin, working with Dmitry on pushing in the initial code contribution. I believe that we can reasonably declare success on project creation. |