-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Triage process draft #134
Triage process draft #134
Conversation
Thanks for submitting your first pull request! You are awesome! 🤗 |
This is a follow-on to #90 , which asks about labeling triaged issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jweill-aws for starting the document.
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
Co-authored-by: Frédéric Collonval <[email protected]>
Co-authored-by: Frédéric Collonval <[email protected]>
@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? |
I would move it to JupyterLab's doc to avoid scattering the source of documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
Closing in favor of jupyterlab/jupyterlab#11661, which addresses jupyterlab/jupyterlab#11660, in |
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.