/
Process for Reviewing and Approving Repository Content
Process for Reviewing and Approving Repository Content
- Topic proposed
- ex: DevOps on z/OS
- WG vote to approve topic and identify where it will be placed in the framework
- Do we need a majority or a super-majority?
- What is the number of meeting attendees required to count as a quorum?
- Members propose content for the topic.
- Whitepapers, articles, blogs, videos, courses, etc
- Original content or pointers to existing content
- Must the content free?
- Not mention a vendor?
- Not behind a registration gate?
- Claims need to be backed up with data/proof.
- WG committee writes our Point of View
- Reviews proposed content as reference material
- As a group, writes an editorial POV
- Curates supporting content based on guidelines and value
- Content distributed to the members for review.
- How many days prior to the vote must we distribute the content?
- Members vote to include content or not.
- Anything declined needs to have deficiencies identified and the nominator given a chance to remedy and resubmit.
Related content
Meeting Notes
Meeting Notes
More like this
Zowe Conformance Program Participation Form
Zowe Conformance Program Participation Form
More like this
Modernization WG Home
Modernization WG Home
More like this
Welcome to Confluence
Welcome to Confluence
More like this
Meetings
More like this
Debian Working Group
Debian Working Group
More like this