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

Create maintainers-minutes-2025-01-31.mdx #3025

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

Conversation

maxulysse
Copy link
Member

@maxulysse maxulysse commented Jan 31, 2025

@netlify /blog/2025/maintainers-minutes-2025-01-31

Copy link

netlify bot commented Jan 31, 2025

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

Name Link
🔨 Latest commit 962b1dc
🔍 Latest deploy log https://app.netlify.com/sites/nf-core-main-site/deploys/67a0bc5e6eb69b0008038d67
😎 Deploy Preview https://deploy-preview-3025--nf-core-main-site.netlify.app/blog/2025/maintainers-minutes-2025-01-31
📱 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 Jan 31, 2025
@maxulysse
Copy link
Member Author

@nf-core-bot fix linting pretty please 🙏

Copy link
Contributor

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

Some small phrasing correction proposals

@maxulysse maxulysse requested a review from itrujnara January 31, 2025 15:45
Copy link
Contributor

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

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

Some comments, mostly adding leading sentences to give more context @maxulysse

We decided that the spring cleaning that we planned to do before the hackathon should be done two weeks before the hackathon.
So it will happen from March 10th to March 14th.
We decided to extend the duration of the spring cleaning to a full week to give everyone enough time to participate.
The idea is to clean up issues, PRs, have a look at the repos and open new issues if needed.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe a expand with a bit more datail, the community might be interested.

E.g. stuff like: we go through common repos, and close PR that are older than X years (After giving a warning), deleting merged branches, we check slack/github teams to make sure they are up to date, archiving pipelines


## References

Maxime Garcia wanted to know about the usage of `conf/igenomes.config`, and how it was actually used in the pipelines.
Copy link
Member

Choose a reason for hiding this comment

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

People do use local cloens of igenomes at least... but I thin ktaht config is the remote onee right?


## Stubs

The discussion about stubs was going a bit in circles and off topic.
Copy link
Member

Choose a reason for hiding this comment

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

What was the discussion about? Have a leading sentence or a bette rtitle


## CI with latest-everything

We widely agreed that since `latest-everything` can break a pipeline, it is important to test with it, because we want our code to be up to date with the latest update.
Copy link
Member

Choose a reason for hiding this comment

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

Why is it breaking? Give more context


We discussed Spring Cleaning once more, and our relentless modules dark knight Simon shared a nice idea:

> We should check our open PRs and close them if they are no longer relevant.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
> We should check our open PRs and close them if they are no longer relevant.
> We should check our own open PRs and close them if they are no longer relevant.

@mashehu
Copy link
Contributor

mashehu commented Feb 3, 2025

@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.

6 participants