Documenting WCRS processes

[mMerlin]

Information posted here will be globally visible. Anyone with an appropriate URL link can find and read it. Anyone with a github account can also add content here, either as new issues, or as comments to existing issue. Authorized accounts can make changes, like adding tags or marking issues as closed.

We should collect and record some of the institutional knowledge for the Society. Get it down some place that will not get lost too easily over time, with changes in the core active members. Some places that information could be stored:

• Google Docs
• Slack
• Github
  • WCRSyyc.github.io
    • store in the repository, and link to from the main https://wcrsyyc.github.io/ page
    • use the wiki
  • a new repository just for this information, using it´s github.io page and/or wiki

We have more control of who can see the content with Google Doc and Slack, but I don't think anything in this category is really private. Mostly of interest to those involved with the WCRS activities, but not really private. Could also be useful to someone else wanting to start up another chapter, so my current thought is one of the github options.

All of the github options can (but do not need to) use markdown for content. The wikis provide their own editor to handle the most common needs. Using github.io provides some extra features, at the cost of increased complexity. That complexity can be reduce with some more documented processes to handle the general use cases. In the same or some other place.

Here is an initial cut at the kind of information I am thinking about here. All of the things we do, that only specific people know much about.

• Saturday Morning museum setup and tear down
• Museum special events (fathers day)
• External Events
  • Maker Faire
  • road trip
  • schools
  • community events
• Maintaining and adding WCRS content
  • https://wcrsyyc.github.io/
  • http://www.robotgames.com/

I think we need to do something, but exactly what and where is open for discussion.