Related to FOSSRIT/tasks#107.

Add page to spell out contacts for FOSS@MAGIC and administrative contacts in our community. Might be cool to leverage FOSS Profiles stuff if it isn't too extra, but the objective is to spell out who is responsible for what.

The cloaks page (from #23) has a table with a lot of info about FOSS members that is really easy to scrape. It'd be appreciated if emails and RIT usernames were removed. While these are technically in the foss_profiles repo, they're not as blatantly easy to scrape there.

Also, usage of [at], like used in #29, is still easy to scrape. If you want email and RIT username to be accessible, it might be better to defer to another location, such as foss_profiles.

Related to FOSSRIT/tasks#107.

Currently I think this is just Namecheap and Mailgun, but I should do a deeper dig through my bookmarks and other FOSS@MAGIC things to confirm.

Write up templates for new issues and pull requests. Makes it easier to facilitate people suggesting new ideas and also helps new contributors review a checklist of things that are helpful for maintainers.

Related to FOSSRIT/tasks#107.

Explain our Matrix presence (rooms, communities, integrations) and how to manage them.

Related to FOSSRIT/tasks#107.

Need more clear documentation about how to use the FOSSRIT/infrastructure repo. Mostly what playbooks are run and how to push new changes out to production.

Related to FOSSRIT/tasks#107.

An at-a-glance overview of how we prepare for the Election Night Hackathon would be helpful.

Related to FOSSRIT/tasks#107.

Not sure if governance or technical yet, but need to spell out how privileges are given out for infrastructure and how someone can get involved with these things.

Related to FOSSRIT/tasks#107.

Sort of related to #13 too, but this is a specific task that needs to be done frequently and should be explicitly documented. Also gives us something to point people at who want to announce something to our community on the website.

In FOSSRIT/fossrit.github.io#85, we are adding a calendar function to the website. This needs to be documented in the FOSSRIT Runbook. @ct-martin wrote docs for the RITlug site here:

https://github.com/RITlug/ritlug.github.io#calendar--placeholders

I'll use that as a base for our own version too.

Related to FOSSRIT/tasks#107.

Explain our Telegram presence and how it is maintained.

Related to FOSSRIT/tasks#107.

• Active repositories
• Teams
• Ownership criteria (?)

I'll think of more soon enough.

Related to FOSSRIT/tasks#107.

Migrate the wiki page below into the Runbook, deprecate the library repo.

https://github.com/FOSSRIT/library/wiki/RIT-IRC-cloaks

Related to FOSSRIT/tasks#107.

Introduce our website, what content goes there, who maintains it, perhaps some other information that isn't specific to contributing. Maybe @ct-martin has some ideas since he has worked on it much more than me.

Related to FOSSRIT/tasks#107.

Some sort of documentation or checklist for things like Maker Faire and Imagine would be helpful for us to fall back on when we start organizing year-to-year. Admittedly a lot of this is in me and @itprofjacobs's heads.

I was looking briefly at the web site open issues when I saw this again. The need remains.

I began listing some things in imperative mood (ie, what is recommended also for git commit messages). It is at best a stub, but perhaps could be a useful starting point or point of comparison with other resources that have been deployed since this issue was opened.

Instead of faffing around a lot more improving it and figuring out where exactly in the RIT stable of resources it should go, I just tossed it into my blog:

http://deejoe.etrumeus.com/update/joining-ritfoss.html

If the CC-BY-SA license on my blog is not suited for some use to which one might want to put it, let me know and we can work something out.

Originally posted by @ritjoe in FOSSRIT/fossrit.github.io#5 (comment)

Related to FOSSRIT/tasks#107.

Document the TeleIRC and Matterbridge services we maintain. Need to coordinate a bit with RITlug here (@Tjzabel, @jrtechs, @hkeena98) since they have graciously allowed us to run these services on their infrastructure.

The website has a complex CI pipeline, where Travis deploys the built source to a production branch. Needs to be detailed and explained because it isn't obvious.

Related to FOSSRIT/tasks#107.

Document where the Discourse service lives, how it works, how to maintain it, etc.

Related to FOSSRIT/tasks#107.

Need to document DigitalOcean FOSS @ RIT MAGIC team and how it relates to things like Discourse (#8).

Related to FOSSRIT/tasks#107.

Try to capture the projects from the FOSSbox and Imagine for a historical reference. This should be maintainer-focused, publicity for our projects should go on the website.

Set up some CODEOWNERS rules, probably with the Tech Team group.