Closed jwflory closed 5 years ago
See issue about RITlug servers in RITlug/runbook#3. Closing issue there and migrating to here.
It was decided in an Eboard meeting to set up a Read the Docs site for our Runbook. Since voting on it, the UI / customization is done and a few docs are already updated. More progress will be made on writing these docs.
See the latest version here: runbook.ritlug.com
@axk4545 @Serubin Both of you have a much better grip of our infrastructure environment than I do. Could I ask both of you to create pages about the machines in our environment in the style of this page (see the reST source for it here)? It would be great if both of you could work together on these pages, between Titan and TigerOS. It might also make more sense to document the different VMs that are in use too.
I'd also like to ask each member of executive board to write an article explaining their role and responsibilities. If you're tech-savvy, you can write this in reStructuredText and submit it as a PR to RITlug/runbook, or you can write it in a DOCX / ODT file and send it to me directly.
Placeholder pages can be found below:
If you'd like to write it yourself in reStructuredText, here's some pages to help you:
@jflory7 You'd think that I have a good grasp...
Will provide documentation on the host setup.
@jflory7 we should also include in this issue updating our constitution or otherwise making it match the runbook.
RITlug/runbook#24 and RITlug/runbook#25 assist towards closing this issue.
Removing end-of-semester milestone. This will not be completed this semester, but I'm still happy with the progress made so far. This work will continue over the summer, and if necessary, into the fall semester. @icflournoy is our new secretary and he'll also help out with the Runbook as needed too.
Stay tuned!
I've made a lot of progress on this over the last year, but I could use some help to complete some of the remaining docs.
@jwflory For the president page, base it off the VP page and make the two explicitly related. Website & Announcements (inc. Talks) pages can be left to me. Otherwise, what do you need help on?
@ct-martin For the eboard position pages, I'd like to have more guidance on this based on the feedback of others too (cc: @Tjzabel @jrtechs).
See this comment for what is left to close this issue.
Adding @Tjzabel, @jrtechs, @icflournoy, and @ct-martin as assignees for RITlug/runbook#49, RITlug/runbook#50, RITlug/runbook#51, and RITlug/runbook#54.
Eboard Comment(9-10-18): We want to update the run-book with our SOP for how we are using the GitHub project board.
We need to update the VP, president, secretary run-book pages with how we are planning the Eboard meeting with the project board.
This task is blocked by RITlug/runbook#62 (pending changes by @icflournoy) and @ct-martin for the website and CampusGroups announcement page. Updating assignee list.
I'm also flagging this one for meeting follow-up to see if can break up the remaining work and try to close this task before the end of September.
RITlug/runbook#66 documents how to send an announcement. Unassigning @Tjzabel.
Summary
Our amazing runbook is slowly starting to date itself – we need to work on updating it based on things we're putting into practice this year or have already changed in the last year
Explanation
The runbook was the holy grail for me and @Serubin when we took over the reins from @thenaterhood and @repkam09. We all know that we're not here forever, so making sure that we keep the runbook updated and current will be helpful not only for ourselves every semester, but also for any forthcoming people who end up running the club past our time too.
I think a sit-down conversation with Eboard first to figure out what we want to update is important first, then an individual or a pair could go through actually making the changes for a final review. Ideally, I think this should happen in 2171 (fall 2017) semester, but it's not exactly a mission-critical task. But the longer it's put off, the worse it will get.