-
Notifications
You must be signed in to change notification settings - Fork 209
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for nf-core-main-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@nf-core-bot fix linting pretty please 🙏 |
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.
Some small phrasing correction proposals
sites/main-site/src/content/blog/2025/maintainers-minutes-2025-01-31.mdx
Outdated
Show resolved
Hide resolved
sites/main-site/src/content/blog/2025/maintainers-minutes-2025-01-31.mdx
Outdated
Show resolved
Hide resolved
sites/main-site/src/content/blog/2025/maintainers-minutes-2025-01-31.mdx
Outdated
Show resolved
Hide resolved
sites/main-site/src/content/blog/2025/maintainers-minutes-2025-01-31.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Igor Trujnara <[email protected]>
sites/main-site/src/content/blog/2025/maintainers-minutes-2025-01-31.mdx
Outdated
Show resolved
Hide resolved
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.
LGTM
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.
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. |
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.
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. |
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.
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. |
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.
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. |
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.
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. |
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.
> 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. |
@nf-core-bot fix linting |
@netlify /blog/2025/maintainers-minutes-2025-01-31