Recap of January 18, 2018, meeting

@juliekuehl review of the work in GitHub

We have an organization page at

We’re going to have a separate repository for each lesson plan.

That’s the repo that I’ve been using as an example to begin with. The idea is that each lesson plan would be its own repo with a file where most of the work is done and an images folder where we could store screenshots. That way they’d be in the same place and easily changed when needed.

Notice there are a bunch of topics associated with the repo. We’ll need to use those to both make our lesson plans searchable as well as use them for our own organizational purposes.

RE: alerts, code sample formatting: the formatting looks to be mostly the same, but I haven’t tested everything. It’s Markdown and not HTML, so there’s that.

@melindahelt: GH has the option to quote things, etc. We should come up with suggested formatting from that.

@juliekuehl: Also, I’ve created a GitHub Page We can use that as a more public-facing page to help organize lesson plans and/or provide additional info to contributors.

@juliekuehl: The other thing I wanted to point out is the organization projects, such as This is what I’m hoping would replace the hot mess spreadsheet as a place to keep track of where things are at.

GitHub account required to view projects but content viewable to all.

@melindahelt: As we talked at WCUS, if someone wants to participate but is against joining GH (say, to just write one lesson plan) they can write and submit ands someone on the team can add it.

@juliekuehl: As far as the process of getting lesson plans into GitHub, it’s pretty manual. It’s a copy and paste from and then doing some reformatting. Then it’s a matter of downloading any images from Make and then uploading them in GitHub. Then switching over the links in the lesson plan.

Standard tools for source control (commits, pulls track issues, etc.) work.

@juliekuehl: I’d love it if everyone would test it out a bit more. Take an exisiting lesson plan and try to bring it into GitHub and see where you get hung up. Play with the projects / issues / pull requests to work out the processes. I’d like to break it learning now before we get serious about moving everything over.

We need to document some of the processes. Things like creating issues and working in the projects. We’ll need some information for other folks who want to help out.

@juliekuehl is working on a screencast to cover much of this.

Perhaps next week we will delegate some of the GitHub tasks, such as setting up the public page and organizing the projects a bit better if needed.

Any questions should be referred to @juliekuehl in Slack.

@estes.chris to take recently edited LPs and move them to GitHub.