|
|
<!----- Conversion time: 1.121 seconds.
|
|
|
|
|
|
|
|
|
Using this Markdown file:
|
|
|
|
|
|
1. Cut and paste this output into your source file.
|
|
|
2. See the notes and action items below regarding this conversion run.
|
|
|
3. Check the rendered output (headings, lists, code blocks, tables) for proper
|
|
|
formatting and use a linkchecker before you publish this page.
|
|
|
|
|
|
Conversion notes:
|
|
|
|
|
|
* Docs to Markdown version 1.0β17
|
|
|
* Wed Jan 08 2020 12:55:20 GMT-0800 (PST)
|
|
|
* Source doc: https://docs.google.com/a/ieee.org/open?id=1bxXmVccgAKNYYg01Q0SCTDRPHY_KcoiCdwkK8dWssKY
|
|
|
----->
|
|
|
|
|
|
|
|
|
<h1>IEEE SA OPEN FAQs </h1>
|
|
|
|
|
|
|
|
|
<h2>INTRODUCTORY QUESTIONS</h2>
|
|
|
|
|
|
|
|
|
**Q: What is Open Source?**
|
|
|
|
|
|
A: Open Source is digital work** **for which the human-readable source code is available—in the preferred form for making modifications—for use, study, re-use, modification, enhancement, and re-distribution by the users. Open Source applies to software and hardware, which may include computer code, hardware designs, data, documentation, documents, and other digital objects.
|
|
|
|
|
|
**Q: What are Contributor License Agreements (CLAs)?**
|
|
|
|
|
|
A: Contributor License Agreements are agreements that each Contributor to IEEE Open Source Projects submits prior to making a Contribution. The CLA provides the rights needed by IEEE to publish the material under an Open Source license. These rights map to the rights that the Open Source license grants to any users of the Open Source. CLAs are available at [https://opensource.ieee.org/community/cla](https://opensource.ieee.org/community/cla). Also see [CLA FAQs].
|
|
|
|
|
|
**Q: Where can I obtain guidance for the role of Maintainer or Committer?**
|
|
|
|
|
|
A: The _IEEE SA Board of Governors (BoG) Open Source Operations Manual _and _Maintainers Manual_ contain guidance on and information about the roles of Maintainer and Committer. You can also direct questions to the IEEE Open Source Community Manager.
|
|
|
|
|
|
**Q: Who is the IEEE SA Open Source Community Manager? IEEE SA Intellectual Property Rights? What are their roles?**
|
|
|
|
|
|
A: The IEEE SA Open Source Community Manager is an IEEE staff role that provides strategic and technical guidance and support to IEEE Open Source Projects. The Community Manager also oversees the operation of the IEEE Open Source Platform, provides guidance to parties interested in initiating Open Source Projects. IEEE SA Intellectual Property Rights is also an IEEE staff role, which is responsible for managing intellectual property matters associated with Open Source Projects, including but not limited to, licenses, IP requirements, and verification of IP compliance.
|
|
|
|
|
|
<h2>GETTING STARTED</h2>
|
|
|
|
|
|
|
|
|
**Q. How can I access the IEEE SA Open Platform? **
|
|
|
|
|
|
**Q. Why am I required to have an IEEE Open Source Platform account in order to log into mattermost **([https://opensource-connect.ieee.org](https://opensource-connect.ieee.org))?
|
|
|
|
|
|
**Q. How do I start a project? **
|
|
|
|
|
|
**Q. What are the features of the IEEE SA Open Source Platform? **
|
|
|
|
|
|
**Q. Does the IEEE offer fiscal sponsorship to open source projects? **
|
|
|
|
|
|
**Q. Am I able to start a new "organization-style" open source project (e.g., similar to the Cloud Native Computing Foundation and their Kubernetes project)? **
|
|
|
|
|
|
**Q. Do you support industry-led, consortium, or association governed open source projects? **
|
|
|
|
|
|
**Q. **
|
|
|
|
|
|
<h2>CONTRIBUTOR LICENSE AGREEMENTS (CLAs)</h2>
|
|
|
|
|
|
|
|
|
**Q: When do I need to submit a Contributor License Agreement?**
|
|
|
|
|
|
A: Contributor License Agreements are submitted prior to making a Contribution to an IEEE Open Source Project.
|
|
|
|
|
|
**Q: What is the difference between an Individual CLA and an Entity CLA?**
|
|
|
|
|
|
A: An Individual CLA is completed by a person who owns the material and any associated IP that the person is submitting to the IEEE Open Source Project. An Entity CLA is completed by a person authorized to grant a license to IEEE on behalf of an entity. Any person authorized to make Contributions on behalf of the entity is listed in the Entity CLA.
|
|
|
|
|
|
**Q: When should I complete Appendix A along with the CLA?**
|
|
|
|
|
|
A: If you are employed by the US Federal Government or are a Crown employee, and cannot provide a license to IEEE for your Contributions, then you must complete Appendix A.
|
|
|
|
|
|
**Q: What are my options for what material a CLA applies to?**
|
|
|
|
|
|
A: There are three options on each CLA that determine to what material the CLA applies. The CLA can apply to 1) all your Contributions to any IEEE Open Source Project, 2) all your Contributions to a specific IEEE Standards Project, or 3) to only the current Contribution to a specific IEEE Standards Project. Each CLA has to indicate how the submitter wants the CLA to apply.
|
|
|
|
|
|
**Q: Are CLA numbers confidential? Who should be permitted to know my CLA number?**
|
|
|
|
|
|
A: Yes, CLA numbers are confidential, and should only be provided to the Maintainer of an IEEE Open Source Project or IEEE staff.
|
|
|
|
|
|
**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).
|
|
|
|
|
|
<h2>FEATURES </h2>
|
|
|
|
|
|
|
|
|
**Q. How do I configure mattermost integration between my projects on the IEEE SA Open Platform and my mattermost channels? **
|
|
|
|
|
|
<h2>OPEN SOURCE AND THE STANDARDS PROCESS</h2>
|
|
|
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**Q: How do I know I am approved to incorporate Open Source in an IEEE SA Project?**
|
|
|
|
|
|
A: If the IEEE SA Standards Board approves a PAR that indicates that Open Source will be incorporated, and shows an approved Open Source license under which the development will occur, then the Working Group is approved to incorporate Open Source in the IEEE SA Project.
|
|
|
|
|
|
**Q: What Open Source licenses are approved for IEEE standards development? Where can I see these licenses?**
|
|
|
|
|
|
A: IEEE SA has currently approved two licenses for use by standards development groups---Apache 2.0 and BSD 3-Clause. These licenses are available from the organizations responsible for those licenses. For Apache 2.0, see the Apache Foundation website at [https://www.apache.org/licenses/LICENSE-2.0](https://www.apache.org/licenses/LICENSE-2.0). For BSD 3-Clause, see the Open Source Initiative website at [https://opensource.org/licenses/BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause).
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**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?**
|
|
|
|
|
|
A: The Working Group should agree on the type of license prior to requesting permission to develop Open Source under that license. A Working Group vote is a good way to document that agreement.
|
|
|
|
|
|
**Q: What is the Working Group Open Source Leadership Team? What does it do?**
|
|
|
|
|
|
A: The Working Group Open Source Leadership Team consists of the Open Source Lead, Maintainer, and other members of the Working Group who will be responsible for addressing submissions to, and updates of, the Open Source, and responding to any comments on the 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.
|
|
|
|
|
|
**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.
|
|
|
|
|
|
**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. \
|
|
|
|
|
|
|
|
|
**Q: Is the Open Source Leadership Team a part of the Comment Resolution Group?**
|
|
|
|
|
|
A: Yes, members of the (WG?) Open Source Leadership Team (at least the Open Source Lead and a Maintainer) shall be a part of the Comment Resolution Group.
|
|
|
|
|
|
**Q: How does the Working Group respond to comments on the Open Source during comment resolution?**
|
|
|
|
|
|
A: All responses to comments on the Open Source shall be included in comment resolution during SA ballot and Public Review.
|
|
|
|
|
|
**Q: How does incorporation of Open Source affect the content of a Working Group draft?**
|
|
|
|
|
|
A: Specific information on CLAs and access to the Open Source is included in the front matter of the draft. In addition, references to Open Source in the draft shall comply with the _IEEE SA Standards Board Operations Manual_ and _IEEE Standards Style Manual_.
|
|
|
|
|
|
**Q: How will the Open Source be made available during Working Group draft development? SA ballot and Public Review? Final publication?**
|
|
|
|
|
|
A: IEEE Open Source incorporated in an IEEE standard will be made available on the IEEE Open Source Platform (opensource.ieee.org) during draft development, SA ballot, Public Review, and final publication.
|
|
|
|
|
|
|
|
|
|
|
|
1. **Q: What should a group consider when determining which Open Source license to use?**
|
|
|
|
|
|
A: <JOSH><Here’s a decent discussion but it includes too much on licneses that we aren’t using [https://heiskr.com/stories/choosing-an-open-source-license](https://heiskr.com/stories/choosing-an-open-source-license)>
|
|
|
|
|
|
2. **Q: What is the difference between a Working Group Open Source Lead and Maintainer? A Maintainer and Committers?**
|
|
|
|
|
|
A: <JOSH>
|
|
|
|
|
|
3. What is the IEEE Open Source Platform?
|
|
|
4. How can I access the IEEE Open Source Platform?
|
|
|
5. Am I able to use my IEEE Open Source Platform account for third party authentication (OAuth2)?
|
|
|
6. Can I connect my GitLab.com, GitHub.com, or social media accounts to my IEEE Open Source Platform account?
|
|
|
7. Why is Continuous Integration and Continuous Development disabled?
|
|
|
8. How do I enable CI/CD for use with my own endpoint?
|
|
|
9. Does the IEEE plan to enable GitLab Pages and to provide a Pages domain?
|
|
|
10. How do I link my own GitLab Pages domain from my project on the IEEE Open Source Platform?
|
|
|
11. How do I create a new mattermost ([https://opensource-connect.ieee.org](https://opensource-connect.ieee.org)) group or channel?
|
|
|
12. Why am I required to have an IEEE Open Source Platform account in order to log into mattermost ([https://opensource-connect.ieee.org](https://opensource-connect.ieee.org))?
|
|
|
13. Can I enable my own bot or connect my mattermost channel to my social media (e.g., twitter) account?
|
|
|
14. How do I configure mattermost integration between my projects on the IEEE Open Source Platform and my mattermost channels?
|
|
|
15. Am I able to collect donations for my open source project through the IEEE Open Source Platform?
|
|
|
16. Am I able to start a new "organization-style" open source project (e.g., similar to the Cloud Native Computing Foundation and their Kubernetes project)?
|
|
|
17. Do you support industry-lead, consortium, or association governed open source projects?
|
|
|
18. Do you plan on providing security or licensing and compliance code scanning or similar functionality similar to those GitHub or GitLab provides in their enterprise offerings?
|
|
|
|
|
|
<!-- Docs to Markdown version 1.0β17 --> |