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

Start september/october maintainer minutes #2819

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

Conversation

jfy133
Copy link
Member

@jfy133 jfy133 commented Oct 27, 2024

@maxulysse I've added some empty places for you to edit :)

@netlify /blog/2024/maintainers-minutes-2024-10-25

Copy link

netlify bot commented Oct 27, 2024

Deploy Preview for nf-core-main-site ready!

Name Link
🔨 Latest commit f8114d5
🔍 Latest deploy log https://app.netlify.com/sites/nf-core-main-site/deploys/671e35f88cd82e00086c6342
😎 Deploy Preview https://deploy-preview-2819--nf-core-main-site.netlify.app/blog/2024/maintainers-minutes-2024-10-25
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot deleted a comment from netlify bot Oct 27, 2024
@jfy133
Copy link
Member Author

jfy133 commented Oct 27, 2024

@nf-core-bot fix linting

It was raised that regularly get almost-complete module PRs, but sometimes they stall because a reviewer leaves comments but does not come back to re-review.
Even if the module author receives a second approving review, but the author often (because we are nice here at nf-core) doesn't feel comfortable merging without getting the approval from the original reviewer.

After a short discussion we felt that we can add a new reviewing guideline that if all (reasonable) comments have been addressed, and an approval has been given by another reviewer, a PR should be merged after 3 months if the original reviewer did not re-review.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
After a short discussion we felt that we can add a new reviewing guideline that if all (reasonable) comments have been addressed, and an approval has been given by another reviewer, a PR should be merged after 3 months if the original reviewer did not re-review.
After a brief discussion, we agreed to introduce a new reviewing guideline: if all reasonable comments have been addressed and another reviewer has approved, the PR should be merged after 3 months if the original reviewer has not returned for a re-review.

Copy link
Contributor

Choose a reason for hiding this comment

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

im thinking maybe 3 months is too long ?? how about 1 month instead ? as I fear if this a nf-core beginner adopter and if they have to report back to their work that can't get it done for another 3 months they might lose interest

Copy link
Contributor

Choose a reason for hiding this comment

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

Also wasn't the problem her the author not the reviewer?

Copy link
Contributor

Choose a reason for hiding this comment

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

well if an author delays, thats their issue I guess. I think the point here is if nf-core reviewers delay the complete review

Copy link
Contributor

Choose a reason for hiding this comment

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

the discussion arose around nf-core/modules#5706, where the module maintainer didn'didn't come back to a PR changing things in their module.

@sateeshperi
Copy link
Contributor

@nf-core-bot fix linting

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.

4 participants