search

jupyterlab / frontends-team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.
https://jupyterlab-team-compass.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
59 stars 30 forks source link

Triage process draft #134

Closed JasonWeill closed 2 years ago

JasonWeill commented 2 years ago

As discussed at the December 8, 2021 JupyterLab meeting, a proposal for triaging issues to ensure that we apply a consistent definition of "Ready" and to prevent issues from remaining open and non-actionable for long periods of time. I welcome your feedback and edits.

welcome[bot] commented 2 years ago

Thanks for submitting your first pull request! You are awesome! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly. welcome You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:

JasonWeill commented 2 years ago

This is a follow-on to #90 , which asks about labeling triaged issues.

JasonWeill commented 2 years ago

I would suggest open the PR against the documentation of JupyterLab to store in it the triage process. A good candidate is https://github.com/jupyterlab/jupyterlab/blame/master/docs/source/developer/contributing.rst#L31

@fcollonval Should I move the triage doc into JupyterLab's docs or should I just mention it in JupyterLab's docs, referring to this file in team-compass?

fcollonval commented 2 years ago

I would move it to JupyterLab's doc to avoid scattering the source of documentation

JasonWeill commented 2 years ago

There are references to both issue & item; was this intended? Should we make this consistent and use "issue" everywhere?

I can use "issue" everywhere, as that's what GitHub uses to describe both bugs and enhancement requests.

JasonWeill commented 2 years ago

Closing in favor of https://github.com/jupyterlab/jupyterlab/pull/11661, which addresses https://github.com/jupyterlab/jupyterlab/issues/11660, in jupyterlab.