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

Initial draft for triaging #901

Open
wants to merge 26 commits into
base: main
Choose a base branch
from
Open

Conversation

Sherwin-14
Copy link
Collaborator

@Sherwin-14 Sherwin-14 commented Dec 15, 2024

This is the initial draft for the triaging document(#754). The pre-commit check is failing because of the use of format argument which seems like a necessity for rendering the doc, more on this here.


📚 Documentation preview 📚: https://earthaccess--901.org.readthedocs.build/en/901/

Copy link

github-actions bot commented Dec 15, 2024

Binder 👈 Launch a binder notebook on this branch for commit 7b7f1aa

I will automatically update this comment whenever this PR is modified

Binder 👈 Launch a binder notebook on this branch for commit 4145cfe

Binder 👈 Launch a binder notebook on this branch for commit a7a182c

Binder 👈 Launch a binder notebook on this branch for commit 9e876f3

Binder 👈 Launch a binder notebook on this branch for commit aa815ff

Binder 👈 Launch a binder notebook on this branch for commit b04d16f

Binder 👈 Launch a binder notebook on this branch for commit 827d79c

Binder 👈 Launch a binder notebook on this branch for commit a9c8ea8

Binder 👈 Launch a binder notebook on this branch for commit 70f2f42

Binder 👈 Launch a binder notebook on this branch for commit 70edb3d

Binder 👈 Launch a binder notebook on this branch for commit 0b939b6

Binder 👈 Launch a binder notebook on this branch for commit e53370f

Binder 👈 Launch a binder notebook on this branch for commit ed81270

Binder 👈 Launch a binder notebook on this branch for commit 5ce45af

Binder 👈 Launch a binder notebook on this branch for commit f41f79c

Binder 👈 Launch a binder notebook on this branch for commit 6c4df6b

Binder 👈 Launch a binder notebook on this branch for commit a2029a5

Binder 👈 Launch a binder notebook on this branch for commit a953c0e

Binder 👈 Launch a binder notebook on this branch for commit c89cb13

Binder 👈 Launch a binder notebook on this branch for commit cabf675

Binder 👈 Launch a binder notebook on this branch for commit 393df4a

Binder 👈 Launch a binder notebook on this branch for commit cf51bad

@Sherwin-14 Sherwin-14 changed the title Triaging initial draft for triaging Dec 15, 2024
@Sherwin-14 Sherwin-14 changed the title initial draft for triaging Initial draft for triaging Dec 15, 2024
@mfisher87
Copy link
Collaborator

mfisher87 commented Dec 15, 2024

Nice work! Will look more closely this week.

Looks like there's a tradeoff to be considered here to fix linting with --unsafe: https://github.com/pre-commit/pre-commit-hooks#check-yaml

@asteiker
Copy link
Member

I'm wondering if some updates may be needed based on the recently closed #760 ? If it would be helpful for me to review and update accordingly, I'd be happy to help.

@mfisher87
Copy link
Collaborator

@asteiker that would be super helpful!!

@mfisher87
Copy link
Collaborator

@asteiker OK to assign this PR to you?

Copy link
Collaborator

@mfisher87 mfisher87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌 Amazing work! Sorry about the number of suggestions here -- we re-organized labels in #760 to be more self-describing, and I think that helps make this document more clear!

CHANGELOG.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
docs/contributing/triaging.md Show resolved Hide resolved
docs/contributing/triaging.md Outdated Show resolved Hide resolved
@mfisher87
Copy link
Collaborator

@asteiker can you also take a look?

mkdocs.yml Show resolved Hide resolved
@Sherwin-14
Copy link
Collaborator Author

@mfisher87 Hey Matt, what about PR triaging workflows? Wouldn't they also be included in the triaging doc?

@mfisher87
Copy link
Collaborator

I'm not sure exactly what you mean here; are you thinking about PR reviews?

@Sherwin-14
Copy link
Collaborator Author

I'm not sure exactly what you mean here; are you thinking about PR reviews?

Yeah PR reviews workflow(I confused it with PR triaging), there is a flowchart for that as well in the repo you linked, should we add that as well to our triaging guide?

@Sherwin-14 Sherwin-14 requested a review from mfisher87 January 14, 2025 16:53
@mfisher87
Copy link
Collaborator

I think it's a great idea! But I would also like to keep this PR focused and get it merged without too much delay. What do you think about dealing with that in another PR?

@mfisher87
Copy link
Collaborator

@Sherwin-14 I'd like to wait to review until the ReadTheDocs build is working again. Do you feel comfortable fixing it? Details here: #901 (comment)

@Sherwin-14
Copy link
Collaborator Author

Sherwin-14 commented Jan 15, 2025

I think it's a great idea! But I would also like to keep this PR focused and get it merged without too much delay. What do you think about dealing with that in another PR?

Sounds good to me :). I also have added the mermaid dependency.

Copy link
Collaborator

@mfisher87 mfisher87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In a rush, just leaving comments :)

mkdocs.yml Outdated Show resolved Hide resolved
- **needs: decision**: We're struggling to decide what to do and the decision committee needs to help.
- **needs: feedback**: Use this label for issues where feedback is requested from the team or our community.
- **needs: help**: Use this label for issues where additional help or contributions are needed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to add back the "good first issue" label, perhaps alone in a "Special labels" section? That is one that triagers should be especially aware of!

start == YES ==> dupe{Is duplicate?}
dupe == YES ==> close2[Close and point to duplicate]
dupe == NO ==> repro{Has proper reproduction?}
repro == NO ==> close3[Label: 'needs reproduction' bot will auto close if no update has been made in 3 days]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bot will auto close if no update has been made in 3 days

I think this isn't true. We have one automation for autoclosing issues, but I believe it's broken: https://github.com/nsidc/earthaccess/blob/main/.github/workflows/issue-manager.yml

We should be careful about fixing it: #895 & https://jacobtomlinson.dev/posts/2024/most-stale-bots-are-anti-user-and-anti-contributor-but-they-dont-have-to-be/

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, I did not made changes to the flowchart since we had discussed earlier, that flowchart will be reviewed. so that is why a lot of irrelevant info is still up there.

Copy link
Collaborator

@mfisher87 mfisher87 Jan 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that makes sense, thanks for the context! I forgot 🙃

Copy link
Collaborator Author

@Sherwin-14 Sherwin-14 Jan 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So how do we move forward from here? I know there might some specific suggestions that you may have in your mind. I think we can encompass all of those in a single review, so it becomes easier for me to add them to the PR :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think getting @asteiker 's eyes on this is probably the best way forward. Will you be at next week's hack day? Maybe we can work together to finalize the flowchart.

real == NO ==> intended{Is the intended behaviour?}
intended == YES ==> explain[Explain and close point to docs if needed]
intended == NO ==> open[Keep open for discussion Remove 'pending triage' label]
real == YES ==> real2["1. Remove 'pending triage' label 2. Add related feature label if applicable (e.g. 'feat: ssr') 3. Add priority and meta labels (see below)"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renders as
image

maj == NO ==> p4[p4: important]
unusable == NO ==> workarounds{Are there workarounds for the bug?}
workarounds == NO ==> p3[p3: minor bug]
workarounds == YES ==> p2[p2: edge case has workaround]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have priority levels yet to my knowledge. @asteiker what do you think?


### Special labels

- **good-first-issue**: Use this label for issues that are suitable for new contributors. These issues are designed to be approachable and not overly complex, making them an ideal starting point for those looking to contribute to the project.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **good-first-issue**: Use this label for issues that are suitable for new contributors. These issues are designed to be approachable and not overly complex, making them an ideal starting point for those looking to contribute to the project.
- **good first issue**: Use this label for issues that are suitable for new contributors. These issues are designed to be approachable and not overly complex, making them an ideal starting point for those looking to contribute to the project.

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.

3 participants