Occupy.net Guidelines

Occupy.net Project Wiki
FLO software tools for the Occupy Movement.

Occupy Tech organizes people to design, develop, deploy and maintain various Occupy.net Services.

Contents

Guidelines 2.0

The intention behind Occupy.net is to help coordinate and support people who want to maintain free/libre/open source software solution for the occupy community.

If you'd like to help maintain one of our existing services, please announce yourself on the service's forum and/or fill out our volunteer form

If you'd like to request a service for Occupy.net to host and/or volunteer to manage a new service, please start a forum thread under the "Occupy.net" forum category.

Process Guidelines

For a service to go from a "request" to "launch", it follows the following process:

Step Stage Task Outcome Documentation Design
1. Request Someone requests a service by describing the desired functionality at forum.occupy.net ticket is created in the Occupy.net PM system na na
2. Evaluate OccupyTech evaluates options and publishes recommendation. recommendation published in wiki Occupy.net Sandbox na
3. Test Recommended solution deployed for testing. software_name.sandbox.occupy.net sandbox PM sub-stream none
4. Alpha Deployed at chosen subdomain and wiki section is created. subdomain.occupy.net wiki page created and support email established occupy.net branding
5. Beta Complied with design and documentation requirements. placed in Occupy.net Nav compliant compliant
6. Launch Integrate single user sign on. press release 24/7 customer service improving

Service Interruptions

When the service is interrupted, the point person is responsible for organising the following response:

  1. Project point person is alerted that their service is interrupted.
  2. They email tech[at]occupy.net to report the problem and being their own investigation.
  3. They create an initial blog post describing the problem and send it to tech[at]occupy.net, where it will be published.
  4. They direct the page to a "temporarily down" page that links to the support section of the tech.occupy.net blog. The page should say something like: ___.Occupy.net Service is temporarily down. It will be back online shortly. If you'd like more info check out the support section on our blog.

Design Guidelines

Guidelines 1.0

Five stage software deployment process:

  1. Request: an individual or group sends a request to the Occupy.net Technology Group by filling out this form. Requests can be for solutions (ex. "our group needs a calendar application"), for hosting (ex. "our group needs you to host software x, which provides us with a calendaring solution"), or a subdomain (ex. "our group deployed software x and we want it to live at calendar.occupy.net").
  2. Evaluation: Occupy.net Tech Team evaluates the free/libre/opensource software options, documents their findings on the wiki and deploys the appropriate solution.
    1. Identify the needs of both the group that made the request and the broader occupy community.
    2. Evaluate the various software tools that could meet the needs of the community and select the option that best meets occupy.net criteria.
    3. Organize a team that deploys and maintains the solution.
    4. Identify and acquires the resources they need to successfully deploy and maintain the solution.
    5. Write a plan for how those resources will be used (including their time, server usage, other costs).
    6. Deploy the software within the Occupy.net development environment.
  3. Alpha (red) products are in the process of being tested by a subset of the occupy.net community. The software is generally unstable and data can be lost at any time. There is no occupy.net branding or support provided for the tool.
    1. Create a project that meets TechOps Project Requirements.
    2. Create a quality assurance (QA) plan that includes use cases, documentation plan, and bug tracking.
    3. Recruit a group of test users and execute the QA plan.
    4. Smash bugs until the product is stable.
    5. Apply Occupy.net branding to the product with navigation bar.
  4. Beta (yellow) products have been considered relatively stable by the occupy.net community and available for general use. There is a backlog of bugs and community members are actively debugging them. The tool may have basic occupy.net branding but it hasn't been fully themed to meet occupy.net brand specifications. A public point person/team is providing support.
    1. Announce the Beta release through the tech blogs, lists and social media profiles accessible to occupy.net.
    2. Offer support with a response time of maximum 48 hours.
    3. Provide a space for product feedback and a plan to address it.
    4. Complete Occupy.net design themeing.
    5. Provide a guide for product users along with recommended usage patterns.
    6. Add Occupy.net Single Sign On.
  5. Launched (green) products are considered entirely stable by the occupy.net community. The bug list hovers around zero. The design is consistent with other launched occupy.net products. The community is providing full support. Single user sign on has been implemented.
    1. Maintain the product so it meeting TechOps Project Requirements.
 
Brought to you by OCCUPY TECH