cci-moc/ops-docs

Mass Open Cloud Operational Polices and Practices

Overview

This repository contains operational policies and practices documentation for the Mass Open Cloud.

Writing new specs

1. Fork this repository.

2. Clone the repository to your local system.

3. Create a new branch for your spec.

4. Create a Policy

   1. Create a new file in policies/ by making a copy of policies/policy-template.md. Specs are numbered; your spec should use the next available number, expressed as a four-digit, zero-padded prefix (such as 0010-my-policy-proposal.md).

5. And/Or a Practice

   1. Create a new file in practices/ by making a copy of practices/practice-template.md. Practices are numbered; your practices should use the next available number, expressed as a four-digit, zero-padded prefix (such as 0010-my-practice-proposal.md).

6. Write a great policy/practice document.

7. Commit your changes to your branch.

8. Push your changes up to your fork.

9. Submit a pull request.

ops-docs's Issues

Create Team Growth practice document

In an effort to expand and better explain the concept behind tracking team growth, I will create a new document in ops-docs/practices to flesh out and expand on the thoughts and reasoning behind the Team Growth Project and its epics.

• create practices doc
• Update templates
• Create a PR for doc

Spike:Add milestone info to ops-doc including how to add milestones

Goal is to use milestones for features/deliverables

• Review options for milestone usage as provided by github
• propose in ops-doc the method to use
• iterate based on team feedback on PR

Write initial draft about our standard software development practices

Kristi to get started on an outline and sync up with the team.

Create format for collecting and storing University and other contact information

• Make/locate a directory
• Discuss - is the directory public or private?
• Private
• Discuss is it just universities, or place for HW partners?
• Any contact information, university, hardware partners, and internal
• first case is northeastern - use as trial run: CCI-MOC/ops-issues#13
• update policies to make it official where we store contact information.
• PR

Update Taxonomy Page to replace Size with Estimation for ZenHub

Update to remove size labels from taxonomy so we don't get confused with ZenHub Estimates.

update documentation for how to update web site and send email when site has problems.

• location of login information for web site
• how to backup wordpress site before changes
• 3 locations to change using elementor
• save files
• which mailing list to send notification to
• who has approval or how to release mail

Document how to discuss and contact MIT

Based on
CCI-MOC/ops-issues#194

• discuss with John Goodhue/Peter/Orran on how to approach
• add contact info to ops docs
• do the thing discussed

Add/update sprint processes to ops-doc

• Update process for starting new sprint
• closing out old sprint (wait a week),
• notes in sprint as an issue.

change search in backlog.md

Search for Adding Cards:

org:CCI-MOC is:open is:issue archived:false

and Select Only show results from linked repositories