Skip to content
Prev 21282 / 21312 Next

[Bioc-devel] strange email

Again trying to automate over thousands is also more challenging.

This is the first stage, Ideally we will build this out more and instead of an email have a website page or link that a maintainer can easily go to on their own and trigger themselves. Email was the easiest to immediately implement.

Now that the associated package has been accepted, once it officially propagates I can direct people to that app so they can clearly see what package(s) are associated and why they have been contacted
https://github.com/Bioconductor/Contributions/issues/4096

This is not about build failures. The build system does that reminder already.  This is about maintainers accepting the code of conduct, licensing, general Bioconductor policies of continuing package maintenance (having active emails, responding to build failures, etc....)



Lori Kern

Bioconductor Core Team

Roswell Park Comprehensive Cancer Center

Department of Biostatistics & Bioinformatics

Elm & Carlton Streets

Buffalo, New York 14263
Message-ID: <BL1PR12MB5301CCA8115010FCB4ABA8AEF966A@BL1PR12MB5301.namprd12.prod.outlook.com>
In-Reply-To: <DS4PR07MB11744512D7BB3F66F04AB1FADAE66A@DS4PR07MB11744.namprd07.prod.outlook.com>