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 ________________________________ From: Geistlinger, Ludwig <[email protected]> Sent: Friday, February 6, 2026 9:29 AM To: [email protected] <[email protected]>; Therneau, Terry M., Ph.D. <[email protected]>; Kern, Lori <[email protected]> Subject: Re: [Bioc-devel] strange email * This email is associated with at least one Bioconductor package. Would it make sense to include the name(s) of the associated Bioconductor package(s) to be more clear? FWIW I was also wondering whether this is a note of a particular build-failure or a general Bioc policy reminder ... Best, Ludwig ________________________________ From: Bioc-devel <[email protected]> on behalf of Kern, Lori via Bioc-devel <[email protected]> Sent: Monday, January 26, 2026 6:29 AM To: [email protected] <[email protected]>; Therneau, Terry M., Ph.D. <[email protected]> Subject: Re: [Bioc-devel] strange email As Vince's reply did not seem to include the mailing list and so others have reference for this report... This is not spam and an effort to ensure maintainer validity and having maintainers acknowledge and accept Bioconductor policies See previous message on this this: https://stat.ethz.ch/pipermail/bioc-devel/2026-January/021262.html<https://secure-web.cisco.com/114yj7KIZ4f-Y8AUYscK77PzvkpEPLGD2wUICeVx79zmQe57H5RXUsLGfF7xp3LiuxJqpchYJwKswIUvxe9R2NnjtnqFP3Fs2Ghs38641NuRiiojH5ZnzpAvbomgkCF-h6WxnYT9DfsoebYxtc5xI5VCoz4Fpe4TRIdaF4Ncei2s3RgujWf2ih-nhV4HEDxxYElvirScmvGGDk4WsDunVy6kS439Tx-49YfYdRmpv7X4BQSw-vlahzFwS5ysLcI93ccue77O7rShO2mIP_vlmDkszHx953jJttQb_glLeoVBtB8f6azrjKCJIwh3d2RM5/https%3A%2F%2Fstat.ethz.ch%2Fpipermail%2Fbioc-devel%2F2026-January%2F021262.html> You received this email because you are the currently listed maintainer of RNASeqPower. Cheers, Lori Kern Bioconductor Core Team Roswell Park Comprehensive Cancer Center Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 ________________________________ From: Bioc-devel <[email protected]> on behalf of Therneau, Terry M., Ph.D. via Bioc-devel <[email protected]> Sent: Sunday, January 25, 2026 10:21 PM To: [email protected] <[email protected]> Subject: [Bioc-devel] strange email I'm getting an email that I need to verify myself "for at least one bioconductor package". But I don't have any bioconductor packages, at least to the best of my knowledge, and it doesn't give any hints. (Nor do I use bioconductor). I am loathe to agree to policies that are irrelevant to me. I know that several bioconductor packages make use of my survival package -- is this spill over from that? If not, how do I either find out what package they are talking about, or stop this spam message? Terry Therneau -- Terry M Therneau, PhD Department of Quantitative Health Sciences Mayo Clinic [email protected] "TERR-ree THUR-noh" [[alternative HTML version deleted]] _______________________________________________ [email protected] mailing list https://secure-web.cisco.com/1-NELNUg0baEg3pEmnJ_pFw-bhaiQhDRIPAf1SdPOXknjzMYLEPF7vUwykkdkl8DzZE_MJmnYuK0PwVCTTT5bFswK9MoXM4FwJC3J_gs0maGubqEfexezWuuSyQTco_--NAg4vm5rkSDu0-lyN_Yg6c8IiNg6B-837Oc2pXuLZ-bgi1tk5eH0fyT3nFnfB9oRv2FtWNJpNi9PKazyBN--jN24RFxs6hhLa3UQAUfMuumSZHZ_8fYLjg3W34yWzsK37g5ivKm0bahCTnJNn3q3xNT2NGQ4_Xg73-VINAJBjR8WU5DC6j8azwzSQNrXe7de/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you. [[alternative HTML version deleted]] _______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel<https://secure-web.cisco.com/1v_2cqsjhOowuOFtQtgmHOhU0x8kInHzR8XvSCUiDEY7Qp7EcN4afR4B7GIrVERnQOusYLWQ6CCIxWPL-KHDa-koGQDR_UM_xkw1mynRegXwGkuKckJupzt27RE7kRjwGwzGmEmpkOrG8HJ3yab3IQpYOukq0cMjSU3ruDoZoGJw33XgSP-Axvfq2srTcM_V3BbbPSUT7KNptQCyaxv597ZnJtoAUyr0TjzqcSjchyogIQJyRotVldoaen6LFrm7EVs1jE9rFbKZWjudV4HaFWFbWd_Y054JT-iwD3v8NCI2XQsm7H9TSDM9nl8RY5ZU0/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-devel> This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you. [[alternative HTML version deleted]] _______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
