... | @@ -65,7 +65,7 @@ A: Yes, CLA numbers are confidential, and should only be provided to the Maintai |
... | @@ -65,7 +65,7 @@ A: Yes, CLA numbers are confidential, and should only be provided to the Maintai |
|
|
|
|
|
**Q: If I have questions on CLAs or Open Source at IEEE, who should I contact?**
|
|
**Q: If I have questions on CLAs or Open Source at IEEE, who should I contact?**
|
|
|
|
|
|
A: Send any questions to [oscontrib@ieee.org](mailto:oscontrib@ieee.org).
|
|
A: Send any CLA or policy questions to [oscontrib@ieee.org](mailto:oscontrib@ieee.org). All other open source questions and requests should be submitted to [opensource@ieee.org](mailto:opensource@ieee.org)
|
|
|
|
|
|
<!--
|
|
<!--
|
|
## FEATURES
|
|
## FEATURES
|
... | @@ -79,19 +79,19 @@ A: Send any questions to [oscontrib@ieee.org](mailto:oscontrib@ieee.org). |
... | @@ -79,19 +79,19 @@ A: Send any questions to [oscontrib@ieee.org](mailto:oscontrib@ieee.org). |
|
|
|
|
|
**Q: By incorporating Open Source, is the IEEE standard also automatically Open Source?**
|
|
**Q: By incorporating Open Source, is the IEEE standard also automatically Open Source?**
|
|
|
|
|
|
A: No. The IEEE standard can be provided separately from the incorporated Open Source, which is available on the IEEE Open Source Platform.
|
|
A: No. The IEEE standard can be provided separately from the incorporated Open Source. The open source material is published publicly on the IEEE Open Source Platform.
|
|
|
|
|
|
**Q: How can I indicate interest in incorporating Open Source as a part of an IEEE SA Project?**
|
|
**Q: How can I indicate interest in incorporating Open Source as a part of an IEEE SA Project?**
|
|
|
|
|
|
A: <JOSH> Until an open source question is added to the PAR form itself, please indicate in the Additional Explanatory Notes section 8.1 and a staff member will contact you to help you through the process.
|
|
A: You are not required to indicate your intent to incorporate open source in the PAR. It is recommended to indicate your intent to incorporate open source in the scope on your PAR, but it is not a requirement.
|
|
|
|
|
|
**Q: Where do I obtain approval to use the IEEE Open Source Platform, and when should I obtain this approval?**
|
|
**Q: Where do I obtain approval to use the IEEE Open Source Platform, and when should I obtain this approval?**
|
|
|
|
|
|
A: Approval for use of the IEEE Open Source Platform is obtained from the IEEE SA Board of Governors Open Source Committee. This approval should be requested prior to submittal of a PAR, and should be obtained prior to NesCom consideration of the PAR.
|
|
A: Approval for use of the IEEE Open Source Platform is obtained from the IEEE SA Board of Governors Open Source Committee. This can be done after approval of the PAR.
|
|
|
|
|
|
**Q: What information about Open Source do I need to include in the PAR, and where would I put this information?**
|
|
**Q: What information about Open Source do I need to include in the PAR, and where would I put this information?**
|
|
|
|
|
|
A: The PAR should include a request to incorporate Open Source in the Project and the license that the Working Group would like to use for the Open Source development. Currently, all information about Open Source must be placed in Section 8.1 of the PAR Form. After the PAR Form is updated, it will include Open Source questions in Section 6 that would need to be completed.
|
|
A: You are not required to indicate your intent to incorporate open source in the PAR. It is recommended to indicate your intent to incorporate open source in the scope on your PAR, but it is not a requirement.
|
|
|
|
|
|
**Q: How do I know I am approved to incorporate Open Source in an IEEE SA Project?**
|
|
**Q: How do I know I am approved to incorporate Open Source in an IEEE SA Project?**
|
|
|
|
|
... | @@ -103,7 +103,7 @@ A: IEEE SA has currently approved two licenses for use by standards development |
... | @@ -103,7 +103,7 @@ A: IEEE SA has currently approved two licenses for use by standards development |
|
|
|
|
|
**Q: How do I choose a license for my project? **
|
|
**Q: How do I choose a license for my project? **
|
|
|
|
|
|
**A: **Email <OS Support email> for questions about the approved options for licenses and for help choosing the license that’s right for your project.
|
|
A: Email opensource@ieee.org for questions about the approved options for licenses and for help choosing the license that’s right for your project.
|
|
|
|
|
|
**Q: Does my Working Group need to vote on what type of license will be applicable for Open Source incorporated in the Working Group’s draft standard?**
|
|
**Q: Does my Working Group need to vote on what type of license will be applicable for Open Source incorporated in the Working Group’s draft standard?**
|
|
|
|
|
... | @@ -115,15 +115,17 @@ A: The Working Group Open Source Leadership Team consists of the Open Source Lea |
... | @@ -115,15 +115,17 @@ A: The Working Group Open Source Leadership Team consists of the Open Source Lea |
|
|
|
|
|
**Q: How will my normal Working Group activities be affected by incorporating Open Source?**
|
|
**Q: How will my normal Working Group activities be affected by incorporating Open Source?**
|
|
|
|
|
|
A: The Working Group will have a subgroup, the Open Source Leadership Team, that will be responsible for coordinating the development of any IEEE Open Source Project incorporated in the draft. If Working Group members would like to contribute to the Open Source, they must submit applicable CLAs for the Open Source Project. Ballot Group members and Public Reviewers must be informed of the incorporation of Open Source prior to initial ballot, and specific Open Source information will be included in the front matter of the draft. Ballot comments will need to indicate comments against the Open Source Project, and the Open Source Leadership Team will need to work with the Comment Resolution Group to respond to comments on the Open Source. RevCom will audit the processes for the consensus ballot as well as the Open Source.
|
|
A: The Working Group will have a subgroup, the Open Source Leadership Team, that will be responsible for coordinating the development of any IEEE Open Source Project incorporated in the draft. If Working Group members would like to contribute to the Open Source, they must submit applicable CLAs for the Open Source Project. Ballot Group members and Public Reviewers must be informed of the incorporation of Open Source prior to initial ballot, and specific Open Source information will be included in the front matter of the draft. Ballot comments will need to indicate comments against the Open Source Project, and the Open Source Leadership Team will need to work with the Comment Resolution Group to respond to comments on the Open Source. RevCom will audit the processes for the consensus ballot as well as the Open Source.
|
|
|
|
|
|
**Q: How will the SA ballot and Public Review be affected by incorporating Open Source?**
|
|
**Q: How will the SA ballot and Public Review be affected by incorporating Open Source?**
|
|
|
|
|
|
A: The Open Source will need to be made available to balloters and public review commenters. Balloters and public review commenters must be informed of the incorporation of Open Source prior to initial ballot, and any commenters on the Open Source requires that they submit an applicable Contributor License Agreement prior to submitting comments. Ballot comments will need to indicate comments against the Open Source Project, and the Open Source Leadership Team will need to work with the Comment Resolution Group to respond to comments on the Open Source.
|
|
A: The Open Source will need to be made available to balloters and public review commenters. Balloters and public review commenters must be informed of the incorporation of Open Source prior to initial ballot. Ballot comments will need to indicate comments against the Open Source Project, and the Open Source Leadership Team will need to work with the Comment Resolution Group to respond to comments on the Open Source.
|
|
|
|
|
|
|
|
If a balloter or public review commentor, wishes to include in their comment an actial contribution to the open source materials (e.g. a patch containing a significant amount of changes to the open source code), then they must submit a CLA, otherwise the Working Group may not be able to consider the Contribution until an applicable CLA is submitted. The Working Group could still consider and respond to the comment itself without a CLA being submitted.
|
|
|
|
|
|
**Q: What if a Contributor does not submit a CLA but proposes changes to Open Source developed by the Working Group?**
|
|
**Q: What if a Contributor does not submit a CLA but proposes changes to Open Source developed by the Working Group?**
|
|
|
|
|
|
A: The Working Group has to inform the Contributor that a CLA must be submitted prior to making a Contribution, and that the Working Group may not be able to consider the Contribution until an applicable CLA is submitted.
|
|
A: If the comment is itself not intended as a Contribution, no CLA is required. If the commentor were you to include in their comment a significant amount of textual changes to the open source code, which usually provided in the form of a patch file or git 'merge request', then this would be a comment that includes in it Contributions to the open source project. The Working Group has to inform the Contributor that a CLA must be submitted prior to making a Contribution to the open source project, and that the Working Group may not be able to consider Contributions to the open source project if it is not submitted under a valid and applicable CLA.
|
|
|
|
|
|
|
|
|
|
**Q: Is the Open Source Leadership Team a part of the Comment Resolution Group?**
|
|
**Q: Is the Open Source Leadership Team a part of the Comment Resolution Group?**
|
... | | ... | |