-
Notifications
You must be signed in to change notification settings - Fork 0
Taskboard How To
All - we are attempting to use Github Projects to track tasks and progress as a publicly viewable Taskboard for the RatPack 2024 Crescendo Robot:
Use this link to view the Taskboard:
This link is public - anyone on the Internet should be able to access it
- so you can show this Taskboard to family/anyone who asks "What are you spending so much time doing at robotics?"
We should normally start a work/build session by checking the Taskboard and choosing a task to work on, or adding the task you will work on
We should review progress and status and update this public Taskboard with that status and any code commits/merge/pull requests, comments, images, videos, etc.
- if you leave early or have additional status to provide, feel free to do that from home or the next day
If you want to review the Github documentation and know more about how to use Github Projects, tasks, and issues - there is a trove of documentation you can dig into here:
The Github Projects Taskboard has multiple views accessible as tabs, so feel free to explore the Week-by-Week, the Grouped-By-Week views
- these views show when the Team started working on tasks
- obviously some tasks and status from prior weeks is missing - team members can feel free to add tasks and status as necessary
- see below to get access to edit and update the Taskboard with your Github ID
- Note: anyone with a Github ID can edit existing tasks, if they are in the public 2023-Tasks repo
The Mech Team and ECS Team (Electrical, Controls, Software) views are filtered so that those teams can focus on just New or Draft tasks along their team columns
As you review the Taskboard, FRC830 Team members should feel free to fill-in status, add images/videos showing status, or add comments to the Task or Issue
- make sure to do this if
- you have a record/photo/video of any of the prototypes that are missing
- you have a memory of doing a task for more than 30 mins that isn't shown on the Taskboard
To add and edit tasks you need a Github username/ID and need to be invited to the FRC830 Github organization by @Alan Stahl
- most of the software team is already on Github and part of the organization
We'll be sending a Google Form out to gather Team member information, including Github IDs, in one place
- the form should take < 2mins to fill out if you already have a Github ID
- once you've filled out the form, you'll be invited to the FRC830 organization by email
- you will need to find the Github email and click through on the link to accept the invitation
If you don't have a Github ID, you can get one here: Github Signup
If you think you have a Github ID, try to login and confirm you can access it
- if you have a Github ID but don't know/remember your password, now is a good time to recover it 😆
- Github: Requesting a new password
- if your Github ID is associated with your old AAPS student-name email address, you can still receive forwarded email using that old address
Github Projects is built upon the Github Issues tracking system and provides everything you can do with Issues and adds some project management features that promote agile development.
The Taskboard displays a number of views as a horizontal row of tabs, showing columns or spreadsheet/tables
- the 1st tab is the agile Kanban view
- this Kanban view shows a series of vertical columns that are "swimlanes" or "parallel tracks" representing work in-progress
- each of the tasks in the columns is displayed as a
card
showing a one-line description of the work or activity- each of the
task cards
has a clickable link that expands the card in a larger edit page where more details can be added or edited- each
task card
can have a detailed description that explains work to be done and supports MarkDown bullet, checkbox, and numeric lists - each
task card
also can be updated with comments, documents, & images/videos/files/etc or links to these artifacts - each
task card
can haveassignees
,labels
,milestones
, iterations by start/workweek
,status
column/track, and custom fields - each
task card
can reference source code blocks, commits or merge/pull requests, other tasks/issues, or external urls
- each
- each of the
New task cards
can be created by:
- clicking the [
➕ Add Item
] link at the bottom of each column - or clicking in a column and pressing the keyboard sequence [
Ctrl
]-[spacebar
] on your keyboard
this allows you to type a one-line task description for the new task card
, or typing the #
symbol for a pop-up to search for an existing issue
in a Github repo
- but this
task card
is just a Draft - it can be moved around, but is not track-able until it is converted to anissue
A Draft task can be converted to a track-able issue
by clicking the ...
icon in the task card
or drilling into the task card
and clicking Convert to issue
If you want to review the Github documentation and know more about how to use Github Projects, tasks, and issues - there is a trove of documentation you can dig into here:
There are a multitude of videos about how to effectively use Github Projects - these are a few I find useful:
This is the YouTube video I showed during the SUnday Jan 22 2023 meeting:
-
YouTube: Organise your GitHub projects with these SUPER project boards - ~8.5 mins
- I find this presenter a little frenetic, but he covers a lot in a short time - I suggest watching at 1.5x or 2x/double-speed and then going back to view specific actions he demonstrates
-
YouTube: Github - Plan and track projects closer to your code - (#DemoDays) - 38+ mins
- this video is presented by one of the Github Projects developers and goes into much more depth on the project management features of Github Projects