code4sac/trash-ai

Write up guide for using project board

Opened this issue · 5 comments

Dependencies

  • #113 : need to figure out why this issue template is not working.

Overview

We need to create a guide for using the label system, new issue templates, and Github project board so that if new team members/PMs would like to contribute, or use this system for their own projects, this can be done easily.

General deadline: end of April

Action Items

  • Research what a good guide would look like. This might be found on the Hack for LA wiki, for example.
  • Determine where the guide will live. Readme file? Google Drive?
  • Make a bullet point outline of all relevant information for the guide
  • Begin filling in the outline, including screenshot examples or video tutorials as needed.
  • Get feedback on a working draft of the guide from people like Mary, Dan, Brianda, Walter, other project leaders...

Resources/Instructions

Check out Hack For LA project boards

Note: figured out why the PR for creating a generic issue template wasn't working... I needed to specify that the file I uploaded "generic template" was either a .yml or a .md file. I created a new .md blank issue template file that is modeled after the templates used by Hack for LA. #136

HfLA uses guides written in google docs to explain how to use their kanban boards for open source projects. See here

Update: guide is ready for review! I can show it off to anyone who is interested

This is my last day with Code for Sac so I'm moving this issue to the ice box until someone else comes along to revive it. The TrashAI project board guide should still be available for anyone who wants to work on it at this link, in the shared google drive. The best way to reach out to me going forward if there are questions on this is through email (epiero2221@gmail.com)