IEEE OS Forms issueshttp://opensource.ieee.org/community/help/forms/-/issues2020-05-05T17:14:12Zhttp://opensource.ieee.org/community/help/forms/-/issues/2gonogo2020-05-05T17:14:12ZJosh Gayj.gay@ieee.orggonogo## Authorization to create a new Official IEEE Open Source Project
### Project Information
1. **Project Name:** Go-No-Go (gonogo)
2. **Project Description:** A simple test open source project.
3. **Background:** This project grew out ...## Authorization to create a new Official IEEE Open Source Project
### Project Information
1. **Project Name:** Go-No-Go (gonogo)
2. **Project Description:** A simple test open source project.
3. **Background:** This project grew out of the urgent problem of needing a test for this inquiry form.
### Leadership and Affiliation
4. **Project leadership:** @jgay
5. **Organization:** IEEE SA
6. **IEEE Standard Development Working Group:** n/a
### Additional info
7. **Governance model:** Lazy Consensus
8. **Related works:** #1
9. **Fiscal sponsorship:** n/a
<!-- Instructions and notes
Submitting this form is the first step in becoming an Official IEEE Open
Source Project. Submission of this form may initiate a conversation with
IEEE staff or the proposed project may move directly to the next step,
which is submission to the Open Source Committee (OSCom) for approval.
IEEE staff shall review requests and will try to provide feedback within ten
working days. Requests for initiating Official IEEE Open Source Projects are
then forwarded to OSCom for review and approval, which takes a minimum of
fourteen calendar days.
Tips:
* Answer what you can: it is OK if you are unable to answer all questions
* Other than listing the names of project leadership and their usernames,
personally identifiable information is not required or recommended.
* HTML comments are not included in the submitted document.
* Instructions and notes can be found at the bottom of this form for select
questions
Q2: If this is an established project, please provide any important background
information, including project age, contributor/developer community, user
base, etc. Links to existing websites and official hosting (e.g., github
page) are appreciated.
Q4: Instructions: Provide the names of the project leadership. if possible,
list their (e.g., "@username"). If you have determined roles such as leads
maintainer, etc. for the project, please indicate the roles as well.
All Official IEEE Open Source projects require that one or more persons
must have the role of Project Lead and Project Maintainer
Q5. If this application is being proposed or lead by an organization, please indicate the organization(s) here.
Q6. If this is a project of an existing standards development working group,
please specify the name of the working and any related standards.
Q7. Please provide any info you can at this time about how you intend for the
governance of this project to be conducted, or put "IEEE Recommendation" if
you wish for IEEE to recommend a default governance model for your project.
Q8. Please describe if and how your project relates to other known
Open Source, open hardware, specifications, or technical standards projects
or similar efforts.
Q9. Please indicate if you are interested in seeking fiscal sponsorship through
the IEEE at this time.
-->
@oscomJosh Gayj.gay@ieee.orgJosh Gayj.gay@ieee.orghttp://opensource.ieee.org/community/help/forms/-/issues/3Test 32020-05-05T17:15:41ZJosh Gayj.gay@ieee.orgTest 3## Authorization to create a new Official IEEE Open Source Project (DRAFT USE ONLY FOR TESTING)
### Project Information
1. **Project Name:**
2. **Project Description:**
3. **Background:**
### Leadership and Affiliation
4. **Project ...## Authorization to create a new Official IEEE Open Source Project (DRAFT USE ONLY FOR TESTING)
### Project Information
1. **Project Name:**
2. **Project Description:**
3. **Background:**
### Leadership and Affiliation
4. **Project leadership:**
5. **Organization:**
6. **IEEE Standard Development Working Group:**
### Additional info
7. **Governance model:**
8. **Related works:**
9. **Fiscal sponsorship:**
<!-- Instructions and notes
Submitting this form is the first step in becoming an Official IEEE Open
Source Project. Submission of this form may initiate a conversation with
IEEE staff or the proposed project may move directly to the next step,
which is submission to the Open Source Committee (OSCom) for approval.
IEEE staff shall review requests and will try to provide feedback within ten
working days. Requests for initiating Official IEEE Open Source Projects are
then forwarded to OSCom for review and approval, which takes a minimum of
fourteen calendar days.
Tips:
* Answer what you can: it is OK if you are unable to answer all questions
* Other than listing the names of project leadership and their usernames,
personally identifiable information is not required or recommended.
* HTML comments are not included in the submitted document.
* Instructions and notes can be found at the bottom of this form for select
questions
Q2: If this is an established project, please provide any important background
information, including project age, contributor/developer community, user
base, etc. Links to existing websites and official hosting (e.g., github
page) are appreciated.
Q4: Instructions: Provide the names of the project leadership. if possible,
list their (e.g., "@username"). If you have determined roles such as leads
maintainer, etc. for the project, please indicate the roles as well.
All Official IEEE Open Source projects require that one or more persons
must have the role of Project Lead and Project Maintainer
Q5. If this application is being proposed or lead by an organization, please
indicate the organization(s) here.
Q6. If this is a project of an existing standards development working group,
please specify the name of the working and any related standards.
Q7. Please provide any info you can at this time about how you intend for the
governance of this project to be conducted, or put "IEEE Recommendation" if
you wish for IEEE to recommend a default governance model for your project.
Q8. Please describe if and how your project relates to other known
Open Source, open hardware, specifications, or technical standards projects
or similar efforts.
Q9. Please indicate if you are interested in seeking fiscal sponsorship through
the IEEE at this time.
-->http://opensource.ieee.org/community/help/forms/-/issues/1tst2020-05-05T17:10:21ZJosh Gayj.gay@ieee.orgtst## Authorization to create a new Official IEEE Open Source Project
<!-- Submitting this form is the first step in becoming an Official IEEE Open
Source Project. Submission of this form may initiate a conversation with
IEEE ...## Authorization to create a new Official IEEE Open Source Project
<!-- Submitting this form is the first step in becoming an Official IEEE Open
Source Project. Submission of this form may initiate a conversation with
IEEE staff or the proposed project may move directly to the next step,
which is submission to the Open Source Committee (OSCom) for approval.
IEEE staff shall review requests and will try to provide feedback within ten
working days. Requests for initiating Official IEEE Open Source Projects are
then forwarded to OSCom for review and approval, which takes a minimum of
fourteen calendar days.
Tips:
* The title should be a short version (slug) of your project name
* Answer what you can: it is OK if you are unable to answer all questions
* Other than listing the names of project leadership and their usernames,
personally identifiable information is not required or recommended.
* HTML comments are not included in the submitted document.
-->
### Project Information
* **Project Name:** tst
* **Project Description:** tst is a very modern test project idea concept
* **Background:** tst was created to test the Official IEEE Open Source project submission issue template.
<!-- If this is an established project, please provide any important background
information, including project age, contributor/developer community, user
base, etc. Links to existing websites and official hosting (e.g., github
page) are appreciated. -->
### Leadership and Affiliation
* **Project leadership:** @jgay
<!-- Instructions: Provide the names of the project leadership. if possible,
list their (e.g., "@username"). If you have determined roles such as lead,
maintainer, etc. for the project, please indicate the roles as well.
All Official IEEE Open Source projcets require that one or more persons
must have the role of Project Lead and Project Maintainer -->
* **Organization:** IEEE SA
<!-- If this application is being proposed or lead by an organization,
please indicate the organization(s) here. -->
* **IEEE Standard Development Working Group:** none
<!-- If this is a project of an existing standards development working group,
please specify the name of the working and any related standards. -->
## Additional info
* **Governance model:** Lazy
<!-- Please provide any info you can at this time about how you intend for the
governance of this project to be conducted, or put "IEEE Recommendation" if
you wish for IEEE to recommend a default governance model for your project.
-->
* **Related works:** None
<!-- please describe if and how your project relates to other known
Open Source, open hardware, specifications, or technical standards projects
or similar efforts. -->
* **Fiscal sponsorship:** Not at this time.
<!-- Please indicate if you are interested in seeking fiscal sponsorship through
the IEEE at this time. -->
## Authorization to create a new Official IEEE Open Source Project
<!-- Submitting this form is the first step in becoming an Official IEEE Open
Source Project. Submission of this form may initiate a conversation with
IEEE staff or the proposed project may move directly to the next step,
which is submission to the Open Source Committee (OSCom) for approval.
IEEE staff shall review requests and will try to provide feedback within ten
working days. Requests for initiating Official IEEE Open Source Projects are
then forwarded to OSCom for review and approval, which takes a minimum of
fourteen calendar days.
Tips:
* The title should be a short version (slug) of your project name
* Answer what you can: it is OK if you are unable to answer all questions
* Other than listing the names of project leadership and their usernames,
personally identifiable information is not required or recommended.
* HTML comments are not included in the submitted document.
-->
### Project Information
* **Project Name:** tst
* **Project Description:** tst is a very modern test project idea concept
* **Background:** tst was created to test the Official IEEE Open Source project submission issue template.
<!-- If this is an established project, please provide any important background
information, including project age, contributor/developer community, user
base, etc. Links to existing websites and official hosting (e.g., github
page) are appreciated. -->
### Leadership and Affiliation
* **Project leadership:** @jgay
<!-- Instructions: Provide the names of the project leadership. if possible,
list their (e.g., "@username"). If you have determined roles such as lead,
maintainer, etc. for the project, please indicate the roles as well.
All Official IEEE Open Source projcets require that one or more persons
must have the role of Project Lead and Project Maintainer -->
* **Organization:** IEEE SA
<!-- If this application is being proposed or lead by an organization,
please indicate the organization(s) here. -->
* **IEEE Standard Development Working Group:** none
<!-- If this is a project of an existing standards development working group,
please specify the name of the working and any related standards. -->
## Additional info
* **Governance model:** Lazy
<!-- Please provide any info you can at this time about how you intend for the
governance of this project to be conducted, or put "IEEE Recommendation" if
you wish for IEEE to recommend a default governance model for your project.
-->
* **Related works:** None
<!-- please describe if and how your project relates to other known
Open Source, open hardware, specifications, or technical standards projects
or similar efforts. -->
* **Fiscal sponsorship:** Not at this time.
<!-- Please indicate if you are interested in seeking fiscal sponsorship through
the IEEE at this time. -->
.
.Josh Gayj.gay@ieee.orgJosh Gayj.gay@ieee.org2020-05-06