How should we use this repo?

[abbycabs]

One issue per task? One issue per meeting, create a list of tasks in that issue? One issue per project? Should we use Projects or ZenHub? What labels should we have?

Leave any thoughts here! We can discuss and decide during our 8/14 team meeting

[chadsansing]

Womp womp (please explain jargon) on "Projects or ZenHub."

Maybe tasks and meetings stay in Docs and we open resources, materials. content, code, etc. here? Labels might then describe content, e.g. "curriculum + online" or "train-the-trainer" + "face-to-face."

Issues could then be about project-related tasks once a draft lands here and exits G-docs-rough-draft-land?

[abbycabs]

Ah, thanks @chadsansing!

• Projects in GitHub lets you use trello-like boards to sort issues: https://github.com/MozillaFoundation/wolo/projects
• ZenHub is a add-on that adds a lot more project management functionality to GitHub. We used it on the software team quite a bit, but the GitHub's new Projects do some of the same things.

Both of these are project management / task tracking. These were helpful for the larger software team with many projects going on at once. Not sure if the ZenHub overhead will be worth it for our smaller team? Projects might be useful though!

I forgot about actually hosting content here! If we want something public-facing (ie on GitHub pages), I'd actually suggest creating separate repos with descriptive names in the Mozilla org instead. But this repo would be good for random smaller things our team wants to centralize.