ritlug / runbook Goto Github PK

The RSS feed for announcements gets watched by an IFTTT hook that posts to the Google Group, however, CampusGroups is not automated and doesn't play well with others. We might get that working sometime in the future, but it won't be the near future. The new process for posting announcements will be something like:

1. Announcement drafted in PR. This allows convenient reviewing.
2. Announcement gets approved by two people on eboard.
3. When the announcement is merged, the merger will also be responsible for posting to CampusGroups [& Slack]

From RITlug/tasks#74, document the email forward from the RIT-issues email to the eboard email

Per previous discussions, our general meetings SOP should be updated to explain how to create an attendance form for signing in and also mention how events are created in CampusGroups (probably on the EMS page since they're done automatically).

Related to RITlug/tasks#54.

A new page is needed to document the RITlug Slack. This is on the backlog for now, but should be written this spring semester.

We need a new page to document the RITlug Telegram group, even though it is officially deprecated and no longer promoted. So long as it exists and we're using it, we need to make a mention of it somewhere.

Currently, documentation is lacking on who is allowed access to Titan, and how access is gained.

I have started a branch to include these changes. Such things I would like to include are:

• How to get access to Titan from Solomon
• What Solomon needs from you to get you access
• How to use the .ovpn file to connect to Titan
• Navigating Proxmox

Problem

We use our project board in order to manage our plethora of issues, but there is no documentation on the board itself.

Solution

Write a page under Administration about the project board and how it is used to organize our workflow.

Onboarding Issues

• Onboarding makes references to the RITlug Facebook which is now discontinued. This should be removed.
• Remove references to club binder. This doesn't exist.
• Add new eboard to RITlug GitLab

Offboarding Issues

• Remove Facebook references
• Add RITlug GitLab bullet

Teleirc is currently a RITlug infrastructure project run out of a Titan VM. I'm the one who has maintained and worked with it, other than @Serubin a couple of times. I can put together an SOP for managing and updating the service either this semester or the next.

Discussed in 2018-08-31 eboard meeting.

As part of closing RITlug/tasks#8, @jrtechs will write a first draft of the "Semester Checklist" page by Monday, September 10th (next eboard meeting).

We suggested to break it into three buckets:

• Before semester
• At start of semester
• Post-semester (i.e. once we get started)

To make it easier to review pull requests, a Travis CI / CircleCI integration should be added to all PRs to test against a Sphinx environment. This will help make it easier to catch breaking changes before pushing them to production.

We need to document how to access the RITlug servers to avoid a repeat of the situation the last 3 years where we knew they existed but had no idea who to contact. We need to ensure we have a way to contact the team that manages the datacenter, the sysadmin team for the Center for Bioscience Education and Technology (Bldg 75)
Rochester Institute of Technology

-where are the servers located?
-who do we contact to access them?
-how do we access them?
any other relevant info.

RITlug has several emails for eboard members that need to be updated during a transition.

Related to RITlug/tasks#8.

Using info from RITlug/tasks#99, make pages describing the committees.

We should document what the process is on getting a design approved through https://campusgroups.rit.edu/clubs.

The website site source is very out of date, and with the new website redesign, now would be a good idea to update this page.

From #34:

...A large section on elections is mostly missing, but will be revisited in the future.

The outcome of #63 lead to the creation of committees, explained RITlug/tasks#99 (comment)

This should be documented in the RITlug Runbook.

How do we manage the RITlug IRC channel?

(Thanks @abkahrs)

Document that we have to contact the relevant department

Problem

There is no documentation on how we run our eboard meetings, or the process on how we prepare for each week's meeting.

Solution

Create a new page under Events documenting the eboard meeting process. This page should include:

• Assigning "review at meeting" label to issues
• Allocating eboard meeting room each semester
• General layout of meetings
• End-of-meeting tasks

With the new R900 being officialized as Olympus, running proxmox, we should take time to document the details of the server once the server is fully set up.

Marking as blocked until proxmox/security fully complete.

Style guidelines, line length, anything worth noting to make accepting new contributions easier on Round 1