GitHub Workflow

[bndnio]

Context

Public place to talk about how we work with GitHub

Outcomes

A document outlining how to work with our GitHub issue handling

Post Jobs

People looking for stuff to do refer to the issues page.

Project managers or anybody that has work,

• Create Issue
• Assign time label
• Assign severity label
• Assign status label
• Assign type label
• Assign person to issue if necessary

New Members

New members can refer to the wiki home page and quickly find background info on the team's seasonal goals, onboarding processes, tutorials, and most importantly a list of ongoing and past projects.

Project Documentation

When working on a project, team members must collect information on their project and produce a standard project document to finalize the completion of their project. Follow the Project Template.

[bndnio]

In particular I'd like to discuss how we can use milestones and projects to group and organize issues without having duplication or too many places to look

[chadjmccolm]

Created the template for the main page in the Wiki and an example project page. The example project page was not completed because I couldn't recall the exact format and the SMUS kids are still in the shop so I can't go reference the whiteboard. Hopefully somebody else can chime in and remember what we decided on or go take a picture of the whiteboard.

[bndnio]

On the main page: this years projects at the top with [in progress] tags as necessary, and sections for each year (each linking to changed projects) Then in each project top is summary, for each year (with the newest at the top): justification, process, a few other headers, and future changes.

[bndnio]

@chadjmccolm @smithbeuvic Hey guys - just noticing the naming of some of the repo's on here are in the form of - or -. What do you think of keeping them as just (in CamelCase) since GitHub takes care of versioning & time stamping for us?