Groups 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 supporting.
Projects that are listed with the appropriate information can access:
- Names and symbols
- Resource raising channels
- Assets and working capital
- Promotion opportunities
The following is a list of fields that we recommend all project fill out.
||statement explaining goals and plans
||Gifting and alternative exchange platform inspired by the #occupy movement.
||Keywords or phrases describing project, comma separated
||website, input form, participatory, research
||point people who are responsible for maintaining project sponsorship
||working group(s) to whom the project reports back
||Technology Operation Group
||NON-OWS groups, organizations, businesses actively organizing or enabling this project, including groups from other OCCUPATIONs/GAs
||ACLU, Occupy Chicago Technology Working Group
||classification of the project's stage of development
||methods of documentation used by the project (pick at least 2)
||Wiki, RSS, Meetings
||URLs to directly relevant online resources for information, data, etc.
||Boolean to indicate whether this project seeks cash donations
||Amount of funds sought
||Boolean to indicate whether this project seeks donations of labor or materials
||Description of donated materials or labor sought
||Laptops, offset print paper, tech and journalism instructors
||a hashtag for promotion and fundraising
||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
||date the project was accepted
||physical location for the project, if applicable
||calendar feed and/or schedule
||general announce list, listserve, etc
InfoHub requests that projects fill out the following additional information:
||date project was listed
||words that define your project. PLEASE SEPARATE USING COMMAS.
||person who facilitated the listing
||person who created the project listing
||email of info contact
||phone number of info contact
||occupy groups collaborating on this project
||individuals and groups outside occupy collaborating on this project
||related projects of the info contact person
||additional info about the project
||comments you have about this form, etc
TechOps requests that projects fill out the following additional information:
||Explanation of what the software should do.
||List of software packages that were considered
||All alpha phase software packages must have a bug list
||All beta phase products must have customized design files
||All launch products must have an active support community space
 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.