Closed jwflory closed 4 years ago
I suggest we break this down into more specific bugs. Lets think about what we can do with just this website. Some suggestions I've seen:
I'd be happy to put this stuff on the website and make it all nice and stuff if someone wants to write the copy.
I think this one is probably best broken into smaller issues just because onboarding is a really big topic and not entirely related to placing it on the website.
I can try working on the copy soon.
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.
Soooo, it's been a while here. Provided that the Runbook is now a thing, and that we now have a functioning website (when this issue was opened, fossrit.github.io was a one-page site about FOSS Hours), I'm going to close this issue as a duplicate
. :clapper:
I opened a new issue, FOSSRIT/runbook#36, to track @ritjoe's above comment.
Problem
When visiting the website, it's unclear how to get involved with FOSS@MAGIC or what you have to do to "be a part of the {club,group,secret society,etc.}".
Analysis
We need to have some clearly documented steps about how a student, either current or incoming, can become involved with the FOSS@MAGIC program. This is a bigger topic than maybe just a website, but as students and alumni, we can maybe offer specific points about how someone can get involved.
A numbered, ordered list of steps that can be accomplished (and easy to think of as "accomplished" or "complete") is needed. The steps would be highlighted on the main page to introduce students for how to participate, things they can try working on to get started, and other ideas for participating. The end result of this "onboarding" guide would be getting "added" to the GitHub organization as a visible form of recognizing the person completing the steps.
This accomplishes the purpose of:
Implementation
[*] Note: I don't want this to be too heavy on "verification" or proving your work… more like a simple check. It's not about indoctrinating people into a secret society or team – we want it to be easy for interested people to become involved and then move up in participation and activity over time.