This proposal was presented and passed at TechOps meetings.
 Proposed Requirements
Our group can work more effectively if members share documentation about the projects they're working on in a standardized manner, and the group is explicit about which projects it's sponsoring.
Projects that are "sponsored" by TechOps receive the following benefits:
- Right to use TechOps's names and symbols.
- Right to contact people who are interested in working with TechOps (ex. volunteer database).
- Right to utilize TechOps resource raising channels (ex. GA proposals, fundraising appeals).
- Access to TechOps working capital (ex. work space, servers, reputation).
- Access to TechOps listing opportunities. (ex. blog, wiki, listserve, newsletter).
 Project Information
'Sponsored' TechOps projects must publish the following information:
||Description of project's status in relation to TechOps
||statement explaining goals and plans
||Gifting and alternative exchange platform inspired by the #occupy movement.
||point people who are responsible for maintaining project sponsorship
||working group(s) to whom the project reports back
||Technology Operation Group
||methods of documentation used by the project (pick at least 2)
||Wiki, RSS, Meetings
||web page describing the project (rec: MediaWiki+RDF)
||updates on a blog (rec: RSS+RDF)
||time/space of working group meeting report backs
||Every Sunday, 6pm EST, TechOps Meeting 60 Wall St
||link to the main website
||link to bug tracker
||link to project management system
||link to source code
||link to support resources
||project's versioning info
||the FLO license(s) that the project has adopted, including a link
||date the project was accepted
||physical location for the project, if applicable
||calendar feed and/or schedule
||general announce list, listserve, etc
 Auditing a Project
Projects can be audited at any general meeting and should be audited when a project point person does a report back. The process is as follows:
- The group reviews project documentation.
- If a project doesn't meet documentation requirements, it's point person must create a documentation plan and deliver it to the group within a given time period.
- If that documentation plan isn't accepted by the group, or the project doesn't meet it's documentation requirements within two weeks of the audit, it loses it's 'sponsored' status.
Excess content from TechOps Project Requirements was not incorporated into this proposal.