Status: Status of issue(e.g. Needs discussion, Help Wanted)
Type: Type of issue(e.g. Bug, Maintenance)
Use only 1 type vs. many
Q&A
Can Brian share the example notebook for visualizing labels?
Very nice. What can be done to make the Tag/Cat: for new contributors more welcoming? Perhaps a color change to make it more visually appealing.
We discussed the possibility of creating a webpage(or GH Project, etc.) to aggregate all of the“New Contributor” issues to make them more accessible to new contributors
Documentation would be one to break out of Tag/Cat: for greater emphasis with a different color.
Uniform colors are hard for me, I’d really like at least different luminosity.
For JupyterHub, I did use some color perception/psychology to choose colors.
Notes can be added to boards, so issues + PRs + notes
Nice overview/report of a project within a specific context
Cons of GH Projects:
Adding cards(issues, PRs) to boards is laborious, drag one card at a time, no automation
Boards quickly become out-of-date
Use cases:
Tracking releases
Better than creating a to do list in an issue, but also more work
Individual to do lists
A nice way for an individual to share what they are currently working on, planning on working on next, later, etc.
Q&A
Ideas for use cases???
Cross-repo use cases?
mimerender-extensions depend heavily on jupyterlab version, so using Projects to track issues related to jupyterlab releases in both jupyterlab and mimerender-extension repos
Overview and the state of Jupyter project management tools (Jamie)
Issue labeling & metrics (Brian & Jason)
GitHub Projects (Grant & Jamie)
MeeSeeks bot (Matthias)