Skip to content
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

Closed
wants to merge 6 commits into from

Conversation

JasonWeill
Copy link
Contributor

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
Copy link

welcome bot commented Dec 9, 2021

Thanks for submitting your first pull request! You are awesome! 🤗

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! 👋

Welcome to the Jupyter community! 🎉

@JasonWeill
Copy link
Contributor Author

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

docs/triage-process.md Outdated Show resolved Hide resolved
Copy link
Member

@fcollonval fcollonval left a 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

docs/triage-process.md Outdated Show resolved Hide resolved
docs/triage-process.md Outdated Show resolved Hide resolved
docs/triage-process.md Outdated Show resolved Hide resolved
docs/triage-process.md Outdated Show resolved Hide resolved
JasonWeill and others added 4 commits December 9, 2021 11:18
Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
Co-authored-by: Frédéric Collonval <fcollonval@users.noreply.github.com>
@JasonWeill
Copy link
Contributor Author

JasonWeill commented Dec 9, 2021

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
Copy link
Member

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

Copy link

@3coins 3coins left a 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?

@JasonWeill
Copy link
Contributor Author

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
Copy link
Contributor Author

Closing in favor of jupyterlab/jupyterlab#11661, which addresses jupyterlab/jupyterlab#11660, in jupyterlab.

@JasonWeill JasonWeill closed this Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants