This would substitute the ~staff/lab_status.yaml file we currently use, which displays urgent announcements on our website. This one is probably easier than the other ones since we probably don't need to make ocflib functions for it if the code to parse the file already exists in ocfweb. Just needs a schema and a small change in ocfweb.

See ocf.io/d/85. This would be used on our officers page and would be the new canonical source of "who is gm/sm currently"

GitHub supports "protecting" branches, only allowing PRs to be merged if they pass certain checks.

This requires using the "status check" feature of GitHub. Basically, we need Jenkins to tell GitHub that a commit hash is OK to be merged. While we have automatic Jenkins builds, none of our repos use the status check feature.

It looks like the GitHub Jenkins plugin supports this (see https://wiki.jenkins.io/display/JENKINS/GitHub+Plugin#GitHubPlugin-Pipelineexamples), so it's just a matter of adding this to the Jenkinsfile. We might also want to put this functionality in the shared pipeline repository if we expect it to be used in other repos.

Would replace ~staff/staff_hours.yaml

Currently in our apphosting vhosts, we have dev-app.ocf.berkeley.edu set up, but it has no aliases (unlike the web testing vhosts, which do have aliases, for instance dev-vhost-alias.ocf.berkeley.edu). It would be nice to have an alias created so that we can test that aliases are still being parsed and loaded by ocflib correctly and test using them on server upgrades.

I've put this in this repo since I'm moving vhost config here (#108) but this could go in ocf/projects or something instead.

Just leaving this here as a reminder as meeting times are still getting finalized but I'll prob update them myself once that's done.

Also it's looking like Web will be meeting at the same time as DDR and Finance is meeting once every two weeks, which may present some problems in ocflib so I'll create an issue there for that as well.

The issue of n-weekly meetings is probably gonna necessitate changes to schemas/meeting_hours.json too, so that's something to keep in mind.

(Possible) schedule copied from meeting 3 slides:

Relavent ocflib issue: ocf/ocflib#242

There was some talk on an ocfstatic issue about getting meeting times to be an API call as opposed to being hard-coded into the website. As it stands, there are a few places in the website that each report staff meetings, but changing one of them means all of them have to be changed.

It might be a good idea then to get a meeting_hours.yaml and meeting_hours.schema.json so we can lay the foundation for this idea. It would operate similar to staff hours, just recording meetings for the different committees instead. I've started some work on this and hopefully I can get a pr soon™.

Also, why do we run puppet specifically on puppet.obe when many different hosts use the etc repo?

I've seen this this happen when two things are building at the same time? There could also be other causes.