Recap of September 12, 2017 Meeting

Flow Chart

@aimeegc intro to flow chart:
“Ok this is a liiiittle bit overwhelming to look at because it’s consolidated into one space. My goal was to capture the pieces everyone has offered and what I’ve heard, and create thematic spaces with subflows inside them (each space). Then, I wanted those to be situated inside a newcomer’s POV, with the two areas they can jump in to participate/help. All of this is architected on the premise that we’re going to try GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner., and knowing/planning for that made this task IMMENSELY easier (aka I got unstuck way faster). I hope that’s a sign that using Github will make organizing this flow IRL immensely easier. Accountability will be a different story, but I am confident that improved visibility of workflow and tagging others will improve accountability.”

Discussion about how to use github for accountability for various tasks.

@pbarthmaier suggested using projects as part of the organization and accountability. He has used it for bug tracking and thinks it could be used for tasks. Unsure about it’s use with free version.

General enthusiasm over using github.

@aimeegc If anyone has comments or questions they can DM her or add comments to the post at

Next Steps

The Hows and the Whos:

1. Organize tested lesson plans and tag WP version under maintenance
2. Assumptions tied to “Become a Tester under “testing.”
3. Assumptions tied to “Test and create feedback” under testing.
4. Assumptions tied to “Move to Maintenance and tag” under testing
5. “May want to revisit support flow in Github context.”
6. Who writes and edits lesson plans?
7. Who on the team gives feedback and assigns an editor?
8. Who edits the plan per the style guide?

@aimeegc: Members of the group with more institutional history should look at the chart and share ideas.

@bethsoderberg “I feel like we’re at a point where we have a lot of questions to digest/things to think through from this conversation. The only concrete action step I can think of other than “ruminate” is “look more closely at Github – both in terms of its general capabilities and in terms of how the parts of the WP project that use it already are using it”

@bethsoderberg: @melindahelt and @juliekuehl and I are figuring out who will set up github.

@bethsoderberg responding to “noisy, but there” resources: We can create documentation to help people know how to do the tasks specifically associated with how we will use it.

@pbarthmaier will be on the point of shepherding the transition to github for users with a wiki or some type of documentation.