Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.ice | ||
|---|---|---|---|
| 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: | andrea.ross, denis.roy, janet.campbell, jayjaybillings, marcel.bruch, mkoegel, richard.burcher, sharon.corbett, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-integrated-computational-environment | ||
| Whiteboard: | |||
| Bug Depends on: | 432038, 432043 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
I've announced the proposal in the "proposals" forum: https://www.eclipse.org/forums/index.php/m/1277323/#msg_1277323 Please monitor that topic for questions. Wayne, Thanks for putting this in play! There were a couple of small edits that I wanted to make before we released it for community review related to the dependencies. Also, did you want the description to be shorter than it is? (I emailed you about this, but hadn't heard back.) Jay (In reply to Jay Billings from comment #2) > There were a couple of small edits that I wanted to make before we released > it for community review related to the dependencies. Also, did you want the > description to be shorter than it is? (I emailed you about this, but hadn't > heard back.) Sorry, my email is a mess from EclipseCon. It'll be a few days before I totally catch up. Feel free to edit the proposal while we're doing the community review. The description is fine in terms of length. We have a means of capturing a summary that we'll use when disseminating information about the project/proposal. Added Marcel to bug CC. He is the projects second mentor. Wayne, Any thoughts on when we will have the Creation Review? We don't need to hurry, but I hadn't heard anything about it. Jay Hi Jay. We're waiting on the trademark review. Apparently it's with external counsel at the moment. We're good-to-go as soon as we secure the trademark. Sorry for the delay. Trademark approved. Creation review scheduled for June 11th. 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 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 Richard, We would like to use the Eclipse.org forge on GitHub, please. The initial contribution is on Sourceforge.net, so the GitHub project will be completely new. Thanks, Jay Congratulations, the project has been successfully created. We will be in touch shortly. Great news! Thanks! 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.ice [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 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 We're working on the initial contribution. Is the correct package prefix org.eclipse.ice or org.eclipse.technology.ice? Jay (In reply to Jay Billings from comment #16) > We're working on the initial contribution. Is the correct package prefix > org.eclipse.ice or org.eclipse.technology.ice? org.eclipse.ice We are almost ready to submit our initial contribution. However, I have a question about the process after that. We can't stop development on our project while we wait for the initial contribution to be cleared. So, there will be some difference in our code base after everything goes through. Is it OK at that point for us to merge our changes into the IC in GitHub so long as they are minor, do no represent a significant difference in capability, and do not bring along any VCS history? If not, what is the best way to see that our changes get into the new repo. Thanks, Jay (In reply to Jay Billings from comment #18) > We can't stop development on our project while we wait for the initial > contribution to be cleared. So, there will be some difference in our code > base after everything goes through. Is it OK at that point for us to merge > our changes into the IC in GitHub so long as they are minor, do no represent > a significant difference in capability, and do not bring along any VCS > history? If not, what is the best way to see that our changes get into the > new repo. You can continue to develop while the IP team reviews the initial contribution. Anything that you commit after the initial contribution must be done so under the terms of the IP Due Diligence process (e.g. committers can just keep working). Make your initial contribution be the first commit in your new GitHub repository. If you have an existing repository that you'd like to move, connect with the webmaster for help. https://github.com/eclipse/ice Let us know if you need assistance. Thanks Wayne! My understanding is that the IC will be the first commit in the new repo, but I have to submit it via a tar ball first and then after it is reviewed someone from the Foundation puts it in the repo, right? I thought I wasn't allowed to just put it over there. (I'm more than happy to do that.) Then, if I read your statement correctly, once it is in the repo we can just start developing on it there while the review progresses? (In reply to Jay Billings from comment #20) > Thanks Wayne! > > My understanding is that the IC will be the first commit in the new repo, > but I have to submit it via a tar ball first and then after it is reviewed > someone from the Foundation puts it in the repo, right? I thought I wasn't > allowed to just put it over there. (I'm more than happy to do that.) > > Then, if I read your statement correctly, once it is in the repo we can just > start developing on it there while the review progresses? Hi Jay, Once the IP team has reviewed and approved the project for Parallel IP, then you will be able to check in the initial contribution as the first commit into the new repository. From that point, the IP team will continue it's detailed review of the initial contribution. You will be able to continue development but will need to adhere to the IP Due Diligence process (e.g. committers can just keep working). The full legal review must be completed before the code is included in a release. HTH, Richard Thanks Richard! Yes, that definitely helps. Jay Hi Folks, Just touching base about the initial contribution. How is it coming? Let us know if you need any help:) My committer tools page does not have a link to IPZilla. Any suggestions? I followed the link below, logged into the Foundation Portal, scrolled to "tools for all committers" and clicked the link. It took me to the "My Eclipse Account" page. I've added a link to IPZilla to the MyAccount page: https://dev.eclipse.org/site_login/myaccount.php In short, IPZilla is here: https://dev.eclipse.org/ipzilla/ (In reply to Jay Billings from comment #24) > My committer tools page does not have a link to IPZilla. Any suggestions? > > I followed the link below, logged into the Foundation Portal, scrolled to > "tools for all committers" and clicked the link. It took me to the "My > Eclipse Account" page. Well... this is embarrassing. Since you weren't listed as a committer on the proposal, you weren't provisioned. This is clearly a problem with our provisioning process that we will address. My apologies. The easiest way to resolve this is to get one of the committers to use the developer portal [1] to nominate you and engage in a committer election. "Jay should have been made a committer in the first place, but your darned system is broken" would be a suitable nomination criteria. If all four existing committers vote +1, then the election will wrap up immediately and we can get you provisioned as quickly as you can provide the required committer paperwork. I'm very sorry for this oversight. If you require assistance in getting this election started (or anything else), please let us know. [1] http://portal.eclipse.org Thanks Wayne! I'll get some my folks to nominate and elect me. Hi Jay, Just adding this as an FYI for the project. No rush on this, we know about Comment 26, so sorry! 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 I'm dealing with one last contribution issue before submitting everything and I came up with a question: Is it OK to release a few bundles under the Eclipse Distribution License and all of the others under EPL? The issue is that I currently fund a developer at another US national lab and his management is strongly against the EPL. They are very pro-BSD though. It would be much easier for us to develop and deploy the product if we had these bundles in the same repo and it would save on some paperwork for the CQ too. Of course, if we can't do it then I'm happy to do the paperwork and jump through some build hoops. (The other option is that he just releases it under BSD to GitHub.) Jay (In reply to Jay Billings from comment #29) > I'm dealing with one last contribution issue before submitting everything > and I came up with a question: Is it OK to release a few bundles under the > Eclipse Distribution License and all of the others under EPL? Projects can release example code under the EDL without having to do anything special. I assume that this isn't the case here. We might consider having Mike connect with the contributor to sort out their concerns with the EPL? Sharon, is what Jay's asking possible? Is it a valid "dual licensing" scenario to have some project code under once license and some under another? (In reply to Jay Billings from comment #29) > I'm dealing with one last contribution issue before submitting everything > and I came up with a question: Is it OK to release a few bundles under the > Eclipse Distribution License and all of the others under EPL? > > The issue is that I currently fund a developer at another US national lab > and his management is strongly against the EPL. They are very pro-BSD though. > > It would be much easier for us to develop and deploy the product if we had > these bundles in the same repo and it would save on some paperwork for the > CQ too. Of course, if we can't do it then I'm happy to do the paperwork and > jump through some build hoops. (The other option is that he just releases it > under BSD to GitHub.) > > Jay Hi Jay, Given the sheer volume of correspondence that the IP Team deals with, we need to limit the number of forums that we use for IP related discussion. For that reason we ask that you direct all IP related questions to emo-ip-team@eclipse.org. We'll be happy to help you. In the interim, I have forwarded your query on your behalf and someone will get back to you shortly. Best regards, Janet I'm trying to create some CQs on IPZilla and it tells me to look in the Portal for the CQ. However, when I look in the portal there is nothing about CQs other than the link to view CQs of interest to ORNL. Clicking on that doesn't do anything than say there are none. Where should I enter CQs? Jay (In reply to Jay Billings from comment #32) > I'm trying to create some CQs on IPZilla and it tells me to look in the > Portal for the CQ. However, when I look in the portal there is nothing about > CQs other than the link to view CQs of interest to ORNL. Clicking on that > doesn't do anything than say there are none. > > Where should I enter CQs? > > Jay Hi Jay, Go to https://projects.eclipse.org/projects/technology.ice. Down the left hand side of the screen you should see a heading named Intellectual Property; underneath that is Create a Contribution Questionnaire. HTH, Richard I have made the changes to the initial contribution that Sharon requested, namely: * Removed build and test data files. Removed third party CMake content * Removed the docs directory * Ice.product and feature.xml files updated to indicate project license * References to the old project URL amended to point to the new project website I am ready to push this to Github, but I don't have rw access to the repo. I set my Github username on my dev login page about an hour ago. Will someone please flip the switch for me or do I need to wait for awhile? Thanks, Jay (In reply to Jay Billings from comment #34) > I am ready to push this to Github, but I don't have rw access to the repo. I > set my Github username on my dev login page about an hour ago. Will someone > please flip the switch for me or do I need to wait for awhile? If I'm correctly reading what I see on GitHub, you should be good-to-go. Let us know if otherwise. Yes, thanks! Someone hooked us up this morning and we just made the IC. Whoo hoo! I've updated the project metadata to include a pointer to the GitHub repo (I also set the Bugzilla reference while I was there). Please take a minute every once-in-a-while to review the metadata to ensure that it's up-to-date. This is where I funnel the community to find information about the project. https://projects.eclipse.org/projects/technology.ice Thanks very much! My plan is to get someone dedicated to updating our metadata. We are going to try to put up a very nice page there instead of just the original proposal. In the past I've had a member of my team dedicated to maintaining this type of information, but she was super brilliant and left for a better gig. (In reply to Jay Billings from comment #36) > Yes, thanks! Someone hooked us up this morning and we just made the IC. Whoo > hoo! Congratulations! This is great news indeed!! I think that we're done here. I think so, yes. :-) I'll start a new bug soon to figure out what we need to do for our first release candidate. We're almost there! |