Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the runbook #8

Closed
jwflory opened this issue Aug 17, 2017 · 15 comments
Closed

Update the runbook #8

jwflory opened this issue Aug 17, 2017 · 15 comments
Assignees
Labels
information Related to information gathering or research priority:high High priority: needs immediate attention

Comments

@jwflory
Copy link
Member

jwflory commented Aug 17, 2017

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.

@jwflory jwflory added EBoard information Related to information gathering or research priority:med Medium priority: doesn't need immediate attention labels Aug 17, 2017
@jwflory
Copy link
Member Author

jwflory commented Oct 2, 2017

See issue about RITlug servers in RITlug/runbook#3. Closing issue there and migrating to here.

@jwflory jwflory added in progress priority:high High priority: needs immediate attention and removed priority:med Medium priority: doesn't need immediate attention labels Oct 10, 2017
@jwflory
Copy link
Member Author

jwflory commented Oct 10, 2017

Progress update

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

Infrastructure

@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.

Roles

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:

Resources

If you'd like to write it yourself in reStructuredText, here's some pages to help you:

@Serubin
Copy link
Member

Serubin commented Oct 10, 2017

@jflory7 You'd think that I have a good grasp...

Will provide documentation on the host setup.

@axk4545
Copy link
Member

axk4545 commented Oct 21, 2017

@jflory7 we should also include in this issue updating our constitution or otherwise making it match the runbook.

@jwflory jwflory added priority:crit Critical priority: this MUST be addressed first and removed priority:high High priority: needs immediate attention labels Jan 19, 2018
@jwflory jwflory added this to the [2175] Spring 2018 milestone Jan 19, 2018
@jwflory jwflory added the review at meeting Ticket suggested for discussion or resolution at next eboard meeting label Sep 1, 2018
jwflory added a commit to RITlug/runbook that referenced this issue Sep 8, 2018
Tjzabel added a commit to RITlug/runbook that referenced this issue Sep 8, 2018
Modernize IRC channel SOP (contributes to RITlug/tasks#8)
@jrtechs
Copy link
Member

jrtechs commented Sep 10, 2018

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.

@Tjzabel Tjzabel removed the review at meeting Ticket suggested for discussion or resolution at next eboard meeting label Sep 11, 2018
@jwflory
Copy link
Member Author

jwflory commented Sep 24, 2018

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.

@jwflory jwflory added priority:high High priority: needs immediate attention review at meeting Ticket suggested for discussion or resolution at next eboard meeting and removed priority:med Medium priority: doesn't need immediate attention labels Sep 24, 2018
@jwflory jwflory assigned Tjzabel and unassigned icflournoy Sep 24, 2018
@icflournoy
Copy link
Member

icflournoy commented Sep 24, 2018

2018-09-24 Eboard Meeting

Discussion

  • Sunset announcements on website, link to archive, indicate that announcements take place on CampusGroups mailing list

Action Items

  • Monday Oct 1st eboard meeting @Tjzabel drafts Announcements page
  • Monday Oct 15th eboard meeting: @ct-martin drafts The Website page changes
  • @jwflory will work on cleaning up / restructuring Meetings page when he adds the sign-in link docs

@jwflory
Copy link
Member Author

jwflory commented Sep 28, 2018

RITlug/runbook#66 documents how to send an announcement. Unassigning @Tjzabel.

@Tjzabel Tjzabel removed the review at meeting Ticket suggested for discussion or resolution at next eboard meeting label Oct 1, 2018
@jwflory jwflory added the review at meeting Ticket suggested for discussion or resolution at next eboard meeting label Oct 15, 2018
@jwflory jwflory removed the review at meeting Ticket suggested for discussion or resolution at next eboard meeting label Oct 17, 2018
@jwflory jwflory closed this as completed Oct 17, 2018
@icflournoy
Copy link
Member

2018-10-17 Eboard Meeting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information Related to information gathering or research priority:high High priority: needs immediate attention
Projects
None yet
Development

No branches or pull requests

7 participants