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.
[edit] Benefits
Projects that are listed with the appropriate information can access:
- Names and symbols
- Contacts
- Resource raising channels
- Assets and working capital
- Promotion opportunities
[edit] Information
[edit] General
The following is a list of fields that we recommend all project fill out.
| Field name |
Wiki Mark-up |
Description |
Example |
| Project name |
proj name |
unique identifier |
PermaBank.net |
| Description |
desc |
statement explaining goals and plans |
Gifting and alternative exchange platform inspired by the #occupy movement. |
| Tags |
tag |
Keywords or phrases describing project, comma separated |
website, input form, participatory, research |
| Contact |
ppeople |
point people who are responsible for maintaining project sponsorship |
devin@sarapisfoundation.org |
| Groups |
wg |
working group(s) to whom the project reports back |
Technology Operation Group |
| Affinity Groups |
ag |
NON-OWS groups, organizations, businesses actively organizing or enabling this project, including groups from other OCCUPATIONs/GAs |
ACLU, Occupy Chicago Technology Working Group |
| Status |
status |
classification of the project's stage of development |
Under Development |
| Documents |
docs |
methods of documentation used by the project (pick at least 2) |
Wiki, RSS, Meetings |
| Information Resources |
infores |
URLs to directly relevant online resources for information, data, etc. |
facebook.com/NYCPrisonSolidarity |
| Cash funding |
donate_cash |
Boolean to indicate whether this project seeks cash donations |
true/false |
| Amount Sought |
donate_cash_amount |
Amount of funds sought |
$1,000,000,000 |
| In-kind Donations |
donate_inkind |
Boolean to indicate whether this project seeks donations of labor or materials |
true/false |
| Materials Sought |
donate_inkind_desc |
Description of donated materials or labor sought |
Laptops, offset print paper, tech and journalism instructors |
| Hashtag |
hashtag |
a hashtag for promotion and fundraising |
#BustUpBofA |
| Page |
proj page |
web page describing the project (rec: MediaWiki+RDF) |
http://wiki.occupy.net/wiki/PermaBank |
|
| updates |
blog |
updates on a blog (rec: RSS+RDF) |
http://tech.nycga.net/category/projects/permabank-net/ |
| Meetings |
meetings |
time/space of working group meeting report backs |
Every Sunday, 6pm EST, TechOps Meeting 60 Wall St |
| Optional:General |
| Date |
date |
date the project was accepted |
9/23/11 |
| Logo |
logo |
graphical representation |
none |
| Location |
geolog |
physical location for the project, if applicable |
global |
| Calendar |
ical |
calendar feed and/or schedule |
none |
| Mailing list |
ml |
general announce list, listserve, etc |
permabank-dev@googlegroups.com |
[edit] InfoHub
InfoHub requests that projects fill out the following additional information:
| Field name |
Wiki Mark-up |
Description |
Example |
| date |
date |
date project was listed |
| tags |
tags |
words that define your project. PLEASE SEPARATE USING COMMAS. |
| interviewer |
interviewer |
person who facilitated the listing |
| info person |
iperson |
person who created the project listing |
| info email |
ipemail |
email of info contact |
| info phone |
iphone |
phone number of info contact |
| occupy partners |
occupy partners |
occupy groups collaborating on this project |
| public partners |
public partners |
individuals and groups outside occupy collaborating on this project |
| related projects |
related projects |
related projects of the info contact person |
| extra info |
extra info |
additional info about the project |
| comments |
comments |
comments you have about this form, etc |
[edit] TechOps
TechOps requests that projects fill out the following additional information:
| Occupy.net Info |
| Request |
request |
Explanation of what the software should do. |
| Evaluation |
evaluation |
List of software packages that were considered |
| Bug list |
bugs |
All alpha phase software packages must have a bug list |
| Design files |
designs |
All beta phase products must have customized design files |
| Support Community |
community |
All launch products must have an active support community space |
[edit] 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.
[edit] Attribution
